Help Exporting Flow with Subflows and Actions as XML – Missing Tables
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 11:43 AM
Hi Team,
I'm working on exporting an entire Flow (from Flow Designer) into an XML file, including its associated subflows, actions, and logic components. I attempted the process using a custom script, but ran into issues – specifically, some of the tables referenced in online examples or documentation, like **sys_hub_subflow**, don't exist in our instance.
Here’s a summary of what I tried:
Wrote a script to export records from tables such as:
sys_hub_flow
sys_hub_flow_action
sys_hub_flow_variable
sys_hub_subflow (this one seems missing)
sys_hub_action_definition
But the script fails or skips components due to some of these tables not being available in our environment. Below are the list of tables I can see in my instance:
Flow: sys_hub_flow
Actions: sys_hub_action_instance
FLow variables: sys_hub_flow_variable
Flow Logic Instance: sys_hub_flow_logic (subflows logics are not stored here)
Questions:
Has anyone successfully exported a full Flow (including all subflows and actions) as XML without using Update Sets?
Are there alternate or newer table names for storing subflow references?
Is there a recommended approach or supported method to achieve this via script or tool?
Any guidance or updated table references would be much appreciated.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2025 03:17 AM
You mention things missing on the environment. First fix that, because it will never work otherwise. Check on version differences, because if you move a flow from a higher to a lower version, it will break 100% guaranteed.
Next to that: check if the store versions are fully up to date, or the same thing happens. You need to be sure that the instances are aligned in this part!!
For the other thing: Why? Why would ever want to do this through scripting/exporting as xml? Really: why? The update set will collect everything. Every action, every trigger, every relation, everything. You can just touch it and it's in the update set. What could possibly be the upside to exporting everything as xml?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark