Hello,

This suggestion is related to this Yammer thread: https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=1817386951745536

The issue

The matter is about library apps.

When we publish a offer, we specify for it supported countries. Any update of the offer (the main app of the App Source submission), the new version of the app is published for all supported countries.

When we publish a library app, the new version of the library is only published for the countries of the offer.

However, it is quite common for a library to be common for several offers. And these offers might not be available in the same countries. As a consequence, if a library is not published with all the offers in way it covers all the countries where this library is available, it results that the latest version of the library might not be available everywhere.

This might cause confusion and might also creates blocking issues when features are deprecated in the library: the new version is not compared with the same previous version in all countries.

As an ISV, we have no summary about which version of the library is available in which country.

The suggestions

I can propose several way to solve this issue:

- A library could be validated and published for all countries where it is already pushed on App Source

OR

- A library could be validated and published for all countries in its AppSourceCop.json

OR

- We could be able to create a hidden offer (without marketing informations) so the app remains hidden in the App Source website but submitted with the same validation process as a normal offer.