You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to submit an update to our certified custom connector. In the past we have provided the commit id for the latest changes in ISV Studio, however this has now been moved to partner centre and requires we provide an SAS link to a .zip file for our connector.
The issue we are experiencing is that the structure of the .zip file outlined in the official documentation does not seem to be accepted by Partner Centre.
There is also of inconsistencies in the documentation for example:
sometimes the files are upper case and sometimes lowercase depending on where you look
sometimes the file needs to contan a Packages.zip, other time its outlined a a Package.zip (notice the plural)
the naming of the folders is different to what is exported from Power automate solutions
Has anyone had any luck with generating a packaged .zip file for ther connector and successfully submitted for review via the partner centre?
Target Date
We would like to publish the change before 19th July 2024
The text was updated successfully, but these errors were encountered:
Description of Feature or Work Requested
Hi Team,
We are trying to submit an update to our certified custom connector. In the past we have provided the commit id for the latest changes in ISV Studio, however this has now been moved to partner centre and requires we provide an SAS link to a .zip file for our connector.
The issue we are experiencing is that the structure of the .zip file outlined in the official documentation does not seem to be accepted by Partner Centre.
There is also of inconsistencies in the documentation for example:
Has anyone had any luck with generating a packaged .zip file for ther connector and successfully submitted for review via the partner centre?
Target Date
We would like to publish the change before 19th July 2024
The text was updated successfully, but these errors were encountered: