on
RE:
As mentioned in a prior comment, this functionality would greatly reduce processing time in the life of a user who is responsible for entering large amounts of data into the system on a daily basis. Everytime a user receives this error message, that another user has modified the record, they lose valuable time having to refresh the page and potentially track down the edits done to the document. An indicator that another user is currently modifying the document (which is widely available on most shared documents), would be a huge time saver.
RE:
It is absolutely critical to be able to sort, filter or export segmentmembers - there should also be a possibility to add / change columns for an export.
RE:
I would add the Settings of an App into Rest APIs. I wish to know how many Apps have been published with the first option - Default Request Access, and the second option - Replace with a custom message, in our organization.
RE:
I would add to the list:(App) whether Access Request setting on an App is Default or Custom Message
RE:
Urgently needed
RE:
A lot of formatting and conditional formatting gets lost when we export the data. It would be great if it retains all those formatting so that the exported file can be shared without additional work.
RE:
It's in outbound... get in real-time asap.
RE:
agreed and upvoted!
RE:
I couldn't agree more with this frustration. Even when using the tenant ID to connect, there still seems to be some leakage from the user's parent organizational workspace (e.g., Connections appear even when on the client tenant). Often, refreshes end up pulling the user back to the parent workspace, as well. It makes supporting clients less than ideal without asking them to create an internal user account, leading to its own challenges.
RE:
A must-have feature for retailers.