Dear Dynamics 365 Business Central team,

It might be good to look into implementing AppSourceCop rule AS0011 for permissionset objects as well, i.e., raise an error (or warning) that tells you that your affix is missing in the object name.
If I am correct, the permission set IDs could clash in the same way as object names for existing object types could (if not, then it would be good to know as well).

If you need any further information, then I am glad to further elaborate.
Category: Development
Ideas Administrator

Thank you for this suggestion! 

As mentioned in comments, this was indeed fixed as part of GitHub request, thus resolving as completed

Business Central R&D team



This has been implemented a few months later after this suggestion was filed. The status of this item could be changed to "COMPLETED".

Category: Development