IDs for actions or/and views?

[APPTandem]

Hello people? What are you struggleling today with?
I usually create a table for my applications to set a menu and a submenu where I define if they view is active or not and who can see it, permissions wise. That way I have a granular control of every view. I was trying to do the same with actions, but looks a little bit harder since it has a lot more of options to set.

Getting to the point, is there a way to have actions or views IDs?
I mean, do they have IDs to use them in expressions?

Thanks in advance

[Kirk_Masden]

To the best of my knowledge, AppSheet doesn’t expose internal IDs for views or actions. You reference them by name as strings.

For views in expressions:

• LINKTOVIEW("MyViewName")
• LINKTOFILTEREDVIEW("ViewName", [Filter Expression])

Actions aren’t invoked via expressions at all—they’re triggered through the UI or automation, and chained by referencing other action names.

Your control table approach for views makes sense, and you can use the view name as your key. For actions, it’s trickier. Action names are usually unique, but it’s possible for a system-generated action and a user-created action to share the same name. So you might need a compound key (action name + associated table) to be safe.

I ran into a similar challenge when building a parser suite that analyzes AppSheet’s Application Documentation export. Even in that HTML file, there are no separate IDs—views appear as <h5 id="viewMyViewName"> and actions as <h5 id="action_MyActionName">. The name itself is the only identifier. Columns are even less unique; you need table name + column name to identify them precisely.

If you’re interested in analyzing app structure and dependencies externally, you might find my parser tools useful. They work with the Application Documentation HTML export:

AppSheet Parser Suite: Analyze and Clean Up Your Apps

Introduction I’ve developed a comprehensive Python tool suite that parses AppSheet’s HTML documentation to help developers understand and maintain their applications. After months of development and debugging, I’m excited to share this with the community. What It Does The AppSheet Parser Suite transforms your app’s HTML documentation export into structured CSV files, revealing: Orphaned components (unused views, actions, columns, slices, format rules) Navigation paths and dependencies between…

[Steve]

@Kirk_Masden

To the best of my knowledge, AppSheet doesn’t expose internal IDs for views or actions.

Correct.

[APPTandem]

Thanks guys for taking the time. How nice would it be to be able to set a table of actions and control their variables.
Thanks anyway!