Suggestion – Improve import tools

[ggcisssca]

Hi,

I use BatchPatch on many computers, then I use often “Export/Import saved commands, deployments, job queues, etc.”

One thing that I found somewhat not funny is the import where it will “merge” settings instead “overwrite / clear current setting and import from scratch”

If I modify something like the description of a command, I export, then import on another computer where it already had older settings identical from previous export… I just get duplicate items.

It is possible to give a choice like at import step where it ask something like that:

– Merge with actual settings, keep current values for those already existing
– Merge with actual settings, overwrite current values if duplicate items exists
– Clear everything and import these new settings

[doug]

We’ll consider this. Thank you.

[jeffallen]

ggcisssca,

I’ve found a way around this problem. Not sure if it’s the best way, but it works for me.

I have new commands every quarter and want the previous quarters commands purged.

Before Batch Patch is opened, delete this hidden file:
C:\Users\<logged_on_username>\AppData\Local\Cocobolo_Software_LLC\BatchPatch\user_defined\user_defined.xml

If you delete the file while BP is open, it’ll just get re-written when you close it.

Now when you open BP, you’ll have a clean slate, and you can go ahead and import your current commands, etc.

Jeff

[Author]

Posts