Save 'Join' for recall

[jakek]

Can we get the functionality to save 'Joins'?  Many times I need to join a table to a feature class, un-join for a variety of reasons, then later re-join the same table.

[JonathanNeal]

Hi @jakek 
I am interested in the variety of reasons you may have to do this.  Can you elaborate on the benifit to this new functionality vs removing and re-adding the join? 

[wayfaringrob]

This would be super useful! I also find myself needing to remove and re-add joins. Sometimes you realize your data isn't quite right, you get updated data/additional fields, you want to try out different datasets, etc. The benefit would be saving time; not having to re-populate all these parameters each time:

[Bud]

I like this idea too. I'm commenting, instead of upvoting, since the upvote button is currently disabled.

Related: Kudo an idea that is flagged as Needs Clarification

[JonathanNeal]

Will close this idea for now to allow clarification to take place since there have been no further comments on it to guide us.
Thoughts:
From @wayfaringrob he would like our SDK option to keep sticky parameters.  Opens the tool with some parameters from history.  Alternatively, maybe open a tool from history?  Maybe save a previous join?

Maybe I am missing something.  I believe these ideas need to have a couple of comments for us to find clarity in what users want.  Please continue to give us feedback, so we can make the software work well for you.

[JonathanNeal]

Please give us feedback, but unsure what experience would best serve users.  Giving a goal, on what you want to solve often can be used to extract the user experience needed.