David,
I am not sure why its working for you. To help you find the issue I have included a youtube video of my issue on the latest 8.0.20.0 beta.
This time I did it with the Company type as I have a problem with that too. So I have a:
Company -> Site -> Host -> Command (as sub connection) tree which will not replace the custom field 1 from either Company or Site.
however
Company -> Site -> Command (as non-subconnection, just a normal session) works fine under the same Company -> Site tree.
I also attached a copy of a Access Data Source file I put this in. We have the same issue in a Enterprise SQL Connection too.
The parrot.cmd file the command entries reference is explained earlier in this thread.
You'll see when I run the command session as a subconnection it doesn't replace the variables.
Note, while building this sample I may have found another issue, or maybe its not supported.
1. I originally built this ACME company tree in our enterprise SQL datasource and verified the problem still existed.
2. I then exported the group as a RDM file.
3. I then made a new Access data source
4. I then imported the RDM file.
5. All the entries showed up but it wasn't a complete export/import. The "Company" and "Site" types for the groups where lost, they both came in just as a "Group" type. Further, neither the Company or Site folders kept their custom defined variables under Information > Other.
I attached the exported file too. From what I can see it doesn't appear the Type of the group or the custom variables are supported during export.
If they are not supported and its not a bug, I think you should warn the user of anything in the tree that won't be exported to the file. I can see somebody exporting a number of trees, thinking they have backups of the data and then importing and realizing they lost a lot of custom setup. It needs to be clear while using the program what is being exported vs. what is not supported. Even if its in a help file or release notes, I can see people being burned by it unless it notifies them during use as the program is pretty intuitive overall (nice work) so if it says "Export..." the assumption is it is exporting everything.
The help files says:
"Exports all session in xml format within a .rdm file that can now be imported into any RDM install. Good for backups but doesn't include credentials (username, domain & password). All data is in clear text."
It makes it clear it doesn't do credentials and the export menu even has another choice for w/ credentials so that is clear when using the program. The help says export is good for backups, but if it doesn't do all the properties then it's not good for backups.
Thanks for all your attention to these posts. The best feature of RDM is the forum and responsiveness to posts/feature requests.
I am not sure why its working for you. To help you find the issue I have included a youtube video of my issue on the latest 8.0.20.0 beta.
This time I did it with the Company type as I have a problem with that too. So I have a:
Company -> Site -> Host -> Command (as sub connection) tree which will not replace the custom field 1 from either Company or Site.
however
Company -> Site -> Command (as non-subconnection, just a normal session) works fine under the same Company -> Site tree.
I also attached a copy of a Access Data Source file I put this in. We have the same issue in a Enterprise SQL Connection too.
The parrot.cmd file the command entries reference is explained earlier in this thread.
You'll see when I run the command session as a subconnection it doesn't replace the variables.
Note, while building this sample I may have found another issue, or maybe its not supported.
1. I originally built this ACME company tree in our enterprise SQL datasource and verified the problem still existed.
2. I then exported the group as a RDM file.
3. I then made a new Access data source
4. I then imported the RDM file.
5. All the entries showed up but it wasn't a complete export/import. The "Company" and "Site" types for the groups where lost, they both came in just as a "Group" type. Further, neither the Company or Site folders kept their custom defined variables under Information > Other.
I attached the exported file too. From what I can see it doesn't appear the Type of the group or the custom variables are supported during export.
If they are not supported and its not a bug, I think you should warn the user of anything in the tree that won't be exported to the file. I can see somebody exporting a number of trees, thinking they have backups of the data and then importing and realizing they lost a lot of custom setup. It needs to be clear while using the program what is being exported vs. what is not supported. Even if its in a help file or release notes, I can see people being burned by it unless it notifies them during use as the program is pretty intuitive overall (nice work) so if it says "Export..." the assumption is it is exporting everything.
The help files says:
"Exports all session in xml format within a .rdm file that can now be imported into any RDM install. Good for backups but doesn't include credentials (username, domain & password). All data is in clear text."
It makes it clear it doesn't do credentials and the export menu even has another choice for w/ credentials so that is clear when using the program. The help says export is good for backups, but if it doesn't do all the properties then it's not good for backups.
Thanks for all your attention to these posts. The best feature of RDM is the forum and responsiveness to posts/feature requests.