Flow designer Complex Objects in Update Sets

[FilipVacula]

Hi folks,

We are creating custom Flow Actions for our scoped application. The actions are using structured objects as their inputs/outputs. During our code review process, we review the contents of the Update Sets.

We have noticed there are large amounts of Complex Object records in the update set, not corresponding to the number of input/output object structures in use. We would like to move the unnecessary records to the Default update set, to prevent promoting unnecessary/leftover records to a higher instance.

Thus, we have 3 questions:

1. Will unused Complex Objects be promoted to a higher instance when committing the Update Set?
2. Can we automatically clean up the unused Complex Objects from the Update Set?
3. How can we identify unused Complex Objects?

Thank you!

[rhysbrennan]

We would also like to know how to map them back to a flow so we can remove them if needed.

I was able to do this for some, but not all from the Flow Inputs table:

I have other that I cannot find, these were also found by our global search configuration on Dictionary Entries. 

Other than causing a mess, I don't think taking them up will cause any issues, other than making potentially making changes that are difficult to identify from the update set.

[Tony102]

Some complex object records are added into my update set every time when I test my flow actions. It's quite annoying. We have so many redundant records of complex objects in our scoped applications and make them hard to maintain.

[Shruti Kamboj]

How you managed it then? I am facing the same problem. What would be the best practice, do we remove it from our update set or delete it or keep it as it is while moving to another environment.