116
We can only find information on BC features that are updated monthly in the release notes.

However, when controlling user permissions on the tables or pages basis, I don't understand how to grant permissions on new tables and pages. We can't figure out which table to refer to as a better customer experience when developing.

We don't want to see how permissions are controlled or developed, we need to see what tables and pages have been added.
Category: Documentation
STATUS DETAILS
Under Review
Ideas Administrator

Thank you for your feedback. We are considering adding it to our (longer term) roadmap.  A more recent suggestion has been closed as a duplicate of this suggestion. Please let the votes and feedback keep coming!
 
Your help is greatly appreciated, 
Eva Dupont
Content PM, Microsoft  

Comments

K

Now that we have permission set extension objects, that should make this kind of thing easier, no?

e.g. extend BASIC or FOUNDATION or whatever, then you don't even have to remember to add that to everyone, just your own permission set that inherits it.

Category: Documentation

K

In an attempt to raise awareness. This is a growing problem that links back to the custom permission sets not being updated when these updates are released. I think we all understand that the addition of new tables, feature development, and functionality makes it difficult to keep an accurate list.

However, this affects every customer environment that we have worked in / on from the late 17's through 18.2 requiring additional work just to get users back in and working. Having such a list is a good proactive step to correcting this so users are not left with an unusable upgraded environment each time one releases.

With the frequency that these updates are rolling out something needs to be done to address this before the experience starts driving users and businesses away.

Category: Documentation

K

You should add eg. 3 fields in admin center under Manage Apps that can be used by you and those responsible for the apps to add links to documents regarding the update. One should be a very short Installation guide (new user permision and fields), short overview and one for detailed description. Thise should be mandatory fields for all updates. As well it would be perfect if Microsoft would make some example of short and usefull documentations in order to standardize the documentation. Another link could eg. be a short userguide that can be handed out to the customer - that would be customer service.
At the moment we are always behind when an update is added even if we find some documentation as they are too big and we dont have time to go though it all.
Hope you like my ide.

Category: Documentation

K

And make the translation so use can understand, and with out, 30 linies of no sense, text we did because .....
20 the same text, which the user have to read, to get to one linie in bad translations to get the msg.

Category: Documentation

K

This would be very helpful to the customers when testing the updates

Category: Documentation