ConnectWise PSA (Independent Publisher)

[howellchrisj]

---

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.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[vmanoharas]

Hi @howellchrisj,

Could you please clarify the below swagger validation error?

##[error]The 'host' property, if present, must be a valid URI host without a scheme or path. ValuePath: /host

[troystaylor]

Hi @howellchrisj,

Could you please clarify the below swagger validation error?

##[error]The 'host' property, if present, must be a valid URI host without a scheme or path. ValuePath: /host

I would recommend setting the host here to something (e.g. microsoft.com) and then using a policy to set it from the connection parameter: https://learn.microsoft.com/en-us/connectors/custom-connectors/policy-templates/dynamichosturl/dynamichosturl

[vmanoharas]

Hi @howellchrisj,
Could you please clarify the below swagger validation error?
##[error]The 'host' property, if present, must be a valid URI host without a scheme or path. ValuePath: /host

I would recommend setting the host here to something (e.g. microsoft.com) and then using a policy to set it from the connection parameter: https://learn.microsoft.com/en-us/connectors/custom-connectors/policy-templates/dynamichosturl/dynamichosturl

Hi @howellchrisj,

Can you please address comments?

[howellchrisj]

@vmanoharas , I adjusted the code to have the URL within the json file per the recommendations. There are two things, one, I changed the Authorization to get an API Key to work and then during that change, I realized that the URL has to be somewhat dynamic as I am using "na", but other countries may need to use "eu" in the URL. For the Default I put it is as the "na", but have the parameter to allow for the change.

[vmanoharas]

@vmanoharas , I adjusted the code to have the URL within the json file per the recommendations. There are two things, one, I changed the Authorization to get an API Key to work and then during that change, I realized that the URL has to be somewhat dynamic as I am using "na", but other countries may need to use "eu" in the URL. For the Default I put it is as the "na", but have the parameter to allow for the change.

Hi @howellchrisj, we would recommend you to test this functionality thoroughly and confirm with us as we will not test this from our end. Additionally, please post the screenshots of successful flow creation.

[howellchrisj]

@vmanoharas , I would love to test this flow. Can you provide me details on how I am supposed to test the connector without the changes being pushed into production? Every time I wrote the custom connector and tried to publish, the exact syntax and json wasn't the same as what it needs to be for the publishing updates.

[vmanoharas]

Hi @howellchrisj,

We would recommend you to refer other IP PRs as they tested and posted the screenshots before we approve. Kindly refer the below links.

https://github.com/microsoft/PowerPlatformConnectors?tab=readme-ov-file#independent-publisher-connectors

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/Independent%20Publisher

https://github.com/microsoft/PowerPlatformConnectors/tree/dev/schemas

[howellchrisj]

Completed the testing and updating of the .json files and tested via Custom Connector

[certificationteam]

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.