It would be nice for certain data sources that you need to connect to multiple times, if you could duplicate a source or use an existing source as a template. this would save time and frustration if all you need to change is a json path or an x-path or if you just need to change one small part of the URI to get the appropriate table.
Linked to this - if using Multi-environment - it would be nice that you could copy the project definition into the Multi-environment definition, and that you can copy from one environment to another (since most of the time you only have to change the server / database)
I really like this idea, Peter! It would greatly speed up the creation and adoption of global databases, which right now is a relatively laborious process compared to how fast everything else is in TimeXtender. Honestly, I think that suggestion might merit its own thread.
Also, re: the original comment, if you create a data source, set it to a global data source, close it, and re-open it, you should find that it's copied all of the global data source settings. These settings stay in the source even if you convert it back to a local connection. I verified that this works for a SQL data source at least.
If you have many settings on a source that you need to add many times, this might allow to you "clone" the source, at least if it's a local source!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
