Markdown Converter (Independent Publisher)

[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.

[certificationteam]

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

Package should contain a readme file

Package should contain a connector package

Package should contain a flow package

[vmanoharas]

Hi @troystaylor,

Could you please follow link and package your files as per the folder structure mentioned below and resubmit the files.

[troystaylor]

@vmanoharas Re-packaged. I would note that the PkgAssets folder seems to be an unnecessary step and that if the intro.md file could be read from the readme.md file as a fallback, then only the single zip with the two zips would be necessary.

[vmanoharas]

Hi @troystaylor,

Thank you for resubmitting the package. However, the package structure is not as expected. Please see the errors below. We request you please run the validation script .

The package zip file should contain a folder ideally named 'PkgAssets' inside 'C:\Users\Markdown Converter.zip\package.zip'.
Please add the folder containing the solution zip files

For a better understanding of how to create a connector package zip file, please refer to the public document placed at https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

Validation failed: Invalid package structure. Check previous messages for details.

[vmanoharas]

Hi @troystaylor,

Still the PkgAssets folder is missing in the folder structure. please run the validation script .

[troystaylor]

@vmanoharas @certificationteam I have updated what I believe is the correct structure now (Windows Compress wasn't adding the folder), but the cmdlet now gives:

The solution zip file 'MarkdownConverterFlow_1_0_0.zip' in 'C:\Users\troy\OneDrive - Hitachi Solutions\Downloads\Markdown Converter\Markdown Converter.zip\package.zip/PkgAssets' should contain 'folder namely 'Connector'.
The folders should match the customization.xml file. They are present by default in an exported solution and should not be modified/removed manually.
Please add the required folder to the solution zip or export the correct solution again.

[vmanoharas]

Hi @troystaylor,

Flow solution folder missing connector folder, please update the package as per the folder structure mentioned above and resubmit the package.

[troystaylor]

@vmanoharas I checked with the Toggl connector PR to confirm, but the Flow solution zip should not contain a Connector.