You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
has been removed and I was planning to use these steps to allow users to update a list view through the metadata service within a transaction rather than giving them permissions to modify metadata all the time.
This leads me to wonder why it was removed - was it a working solution that I should still attempt without having the steps for reference anymore? Was it removed because it was not a viable solution? Is there a better solution available or should I not attempt something like this?
To explain my use case more - I created a LWC button that passes a record ID and uses the metadata service to update a specific list view to filter based off of the record ID. This works fabulously for admins but not standard users without the correct permissions. I would love a way to allow for these permissions to update the list view through the metadata api only while the transaction is running. The blog post if I remember correctly suggested creating a connected app, using named credentials of a user with a profile that has these permissions to essentially "log in" as them while the transaction runs.
The text was updated successfully, but these errors were encountered:
I wonder if maybe the link is just bad. I searched the title of the article, and found a very similarly-named one from the same domain -- might be the same one:
The link
Using Named Credentials with the Apex Wrapper Salesforce Metadata API (apex-mdapi)
has been removed and I was planning to use these steps to allow users to update a list view through the metadata service within a transaction rather than giving them permissions to modify metadata all the time.
This leads me to wonder why it was removed - was it a working solution that I should still attempt without having the steps for reference anymore? Was it removed because it was not a viable solution? Is there a better solution available or should I not attempt something like this?
To explain my use case more - I created a LWC button that passes a record ID and uses the metadata service to update a specific list view to filter based off of the record ID. This works fabulously for admins but not standard users without the correct permissions. I would love a way to allow for these permissions to update the list view through the metadata api only while the transaction is running. The blog post if I remember correctly suggested creating a connected app, using named credentials of a user with a profile that has these permissions to essentially "log in" as them while the transaction runs.
The text was updated successfully, but these errors were encountered: