Skip to content

Conversation

@aressler38
Copy link
Contributor

@aressler38 aressler38 commented Oct 20, 2025


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.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

  - Inline request objects for better UI presentation
  - Annotate visibility options
  - Add specific descriptions for responses
@aressler38 aressler38 requested a review from a team as a code owner October 20, 2025 21:35
@aressler38
Copy link
Contributor Author

We expect this to be our last update to the dev branch and are ready to proceed with the certification process.
In this change, we've done the following:

  • Inline request objects for better UI presentation
  • Annotate visibility options (x-ms-visibility)
  • Add specific descriptions for responses

This connector is not yet in the Power Platform. There was prior discussion relating to updating this connector in the dev branch in the last PR we submitted: #3976. We are preparing the files for the certification process now that we've completed all desired changes.

@vmanoharas
Copy link
Contributor

Hi @aressler38,

Swagger validation encountered below error, could you please confirm that this change will not break the existing flows?

##[error]The operation has been deleted. This change breaks existing flows. ValuePath: operation/GetOperationId Source: NewSwagger
##[error]The input field has been changed from optional to required. ValuePath: operation/SuggestEndpointRemediation/parameter/body/schema/issue/required Source: NewSwagger

@aressler38
Copy link
Contributor Author

Hi @vmanoharas,

This is an expected change, and it doesn't break any existing flows. Right now, the connector is going through the first certification process. We submitted the zip package. The reason for this change is that the operation was confusing the Copilot gpt5 agent because the operation doesn't actually return an ID. It returns the operation object. After updating our prompting and fixing this operation, our connector is now ready and going through the certification process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants