Stable User Access Export

Question

Hi all,

Has anyone found a way of exporting User Access from a saved view rather than directly from the Users tab?

We're feeding the export into Azure Blob Storage and have had a couple of issues recently where changes to the standard Users export altered the filename/structure, impacting downstream processes.

Ideally, we'd like a more stable export that we control via a saved view. Has anyone implemented something similar?

Thanks.

jasonblinn · Answer

One more option (And im not saying this is the best option for you, just an option) here would be to think of changing where the user access is maintained. If you maintain it in a module, and then import it into the users tab, vs maintaining it in the users tab and getting it out, then you already have a module that could be used for export purposes.

Some things to consider here include if you use the users list, then only user with access to the model will be present, and anyone with No Access is removed. You also have to build the module, lists, and actions to support this.

This could also help with the time that it takes to add a user to the model as it would cause one re-calculation via import compared to doing it manually where it re-calcs every time a user is added.

Just something to think about!

tfearns · Answer

Thanks, this is useful and something we do in another area. Glad we're not missing anything obvious  😊

seymatas1 · Answer

This is the only way I can think of:

1. Export to Azure Blob storage (you already do this)

2. Pull the file into the module.

3. Transform it to a standard format.

4. Export it back to Blob.

(I would skip step 2 and transform the file in Azure. )

There will be selective access and maintenance complexities.

Also, monitoring the release calendar closely and preparing for changes is the most efficient solution.