DCP v3

[poweraddons]

---

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.

[Amjed-Ayoub]

Hello @poweraddons,
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirements, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this page at step 6.
Please Create an environment in the Preview region. You will use this environment later to test your connector after Microsoft is done with the functional verification for your connector.
We expect all tests to be completed within 1-2 weeks.
If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.
Please let me know if you have any questions or run into any problems while creating or updating your submission.
Thank you very much for working with us.

[poweraddons]

Hi!
I have 3 questions now after I tested the connector in the preview instance:

1. Do I need to upload the intro.md with my artifacts in my pull request, or do I still need to upload it in the isv studio in the activity control?
2. I have two steps in the preview instance visible that are defined as depreciated in our apiDefinition.swagger.json. Can you tell me why? We have multiple steps that are depreciated, but only 2 are visible.
3. It looks like I have to have set the "allowSharing=true" in my artifacts, but do not find a documenation for that. Can you point me into the right direction?
   

[Amjed-Ayoub]

Hello @poweraddons yes please add your intro.md in the activity control area in ISV Studio. this file is not required in the open source repo.
regarding number 2 and 3 please see our docs here.

I would like to share our Power Automate Forum with you, If you have development questions, this is where you can review answers to existing questions or submit a new question.
I would also suggest you use the activity control area to reach out to our engineers directly.

I hope this helps.

Thank you so much again.

[poweraddons]

Hi!
The problem is that we followed exactly the steps described in the docs for depreciated operations, and it works for 10 of 12 and the allowSharing=true is nowhere described.
For both issues, I do not think the forum can help and in the activity control I still got no answer to my questions.

Do you have an idea who can help ?

[Amjed-Ayoub]

Hello @poweraddons,

Thank you for the confirmation.

Yes, this property can be added by our engineer internally, we will work with our infrastructure team to make this change on your behalf.
Can you please confirm if you want us to proceed and add this property to your connector?

I look forward to hearing from you.

Thank you so much again.

[poweraddons]

Hi @Amjed-Ayoub ,
yes, please add this property to our connector.

We had this already in v1, but now in v2 and v3 I miss it. Can you tell me why that not set in v2 and v3 ?
Do I have to ask you to add this allowsharing for each version I publish?