Scenario: I am currently working with FinOps version 10.0.2263.172. I then receive a link to a isv package that I download and implement into my local metadata folder.

Problem:

Hereafter lots of problems occurs trying to work with model management - in few words nothing is working!

Solution:

When isv binary packages are included in custom metadat folders, VS checks if they are of same version as the reference metadata in the PackagesLocalDirectory folder received from PPAC/UDE.

Win:

Not spending days searching for the reason to weak error message in VS before uploading isv packages to asset library and there be able to see that the package is for a different PU!