Mock Data Generator (Independent Publisher) Code-only

[troystaylor]

---

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 @troystaylor,

Our IP connector certification process has been changed. Kindly refer the below link. As per the process, we have shared a MS Form through email to the email that you mentioned in the swagger file. Please fill the form to proceed for the next process and please reply here once the form is filled.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification

[vmanoharas]

Hi @troystaylor,

Could you please upload package zip file?

[troystaylor]

@vmanoharas Zip file uploaded.

[vmanoharas]

certify-connector

[certificationteam]

We reviewed your submission and identified some changes that are needed before we can publish or update the connector.Kindly make the following changes and resubmit the request for certification.You can refer here to understand more about the error codes and how to fix them.

Many Thanks,
Copilot Connector Certification Team

Error(s) are:

1. Package should contain an icon.

[vmanoharas]

We reviewed your submission and identified some changes that are needed before we can publish or update the connector.Kindly make the following changes and resubmit the request for certification.You can refer here to understand more about the error codes and how to fix them.

Many Thanks, Copilot Connector Certification Team

Error(s) are:

1. Package should contain an icon.

Hi @troystaylor,

Please fix above error and resubmit package.

[troystaylor]

@vmanoharas Independent Publisher connectors requiring an icon sounds like an automation error.

[vmanoharas]

Hi @troystaylor,

Yes you are correct, IP connectors not required to have icon, however the automation tool is same for VP and IP connector. We will improve the automation tool in future. Could you please add default icon and upload the package?

Thank you for your patience and understanding.