-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Merge to PowePlatform #3712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge to PowePlatform #3712
Conversation
Merge from microsoft/PowerPlatformConnectors dev
getting latest
taking latest
Merge from powerplatform
merge from PowerPlatform
merge from PowerPlatform
merge to pdf4me
merge from powerautomate
new word methods for PDF4me
merge from powerplatform
adding new image processing methods to PDF4me
adding new fill a pdf form method
merge from power platform
Merge from Power Platform
Adding EPC QR Code action to PDF4me
Added new PDF4me feature prepare for print
merge from powerplatform
updating attachment format
|
Hello @varunynoox, can you please confirm that existing flows will not break from the swagger validation errors below? The type format has been changed for the input field. Existing flows will continue to send the field with the old type format. ValuePath: operation/AddAttachmentToPdf_v1/parameter/body/schema/document/Name/format Source: NewSwagger The type format has been changed for the input field. Existing flows will continue to send the field with the old type format. ValuePath: operation/AddAttachmentToPdf_v1/parameter/body/schema/attachments/items/docContent/format Source: NewSwagger |
|
The existing flow will not break. They are not working as required hence the change. |
Thank you for the confirmation! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dear Partner,
Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors & Plugins. Read the blog here- Announcing Partner Center to certify and publish Power Platform Copilot Connectors and Plugins - Microsoft Power Platform Blog
As next steps:
- Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
- Package your connector and plugin files- Prepare Power Platform connector and plugin files for certification
- Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
- Initiate a certification request in Partner Center- Verified publisher certification process
- Ensure your connector & plugin files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
- Test your connector post certification to provide go-live for deployment- Testing Guidelines
- If you wish to Update your connector or plugin in future- Updating Guidelines
For any queries or concerns please get in touch with us on certificationteam@microsoft.com
Many thanks,
Power Platform
Copilot connector & plugin certification team
When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process: