User Variables allowed for RVTools exports?

Hello Chuck,

Thank you for reaching out to us regarding this,

I see, I believe that should work, but I have not tested this myself at this time, is the variable not being resolved as expected when you generate this export?

Let me know,

Best regards,

Sam,

I have not tried because I did not know if this is possible.

Do you happen to have a link or any FAQ's as to what variables are available within RDM?

Thanks!

Hello Chuck,

Regarding the use of variables with the RVTools Export function in RDM, they should theoretically be supported throughout various functionalities as variables are generally well integrated. However, there might be specific cases where the integration might not be perfect due to overlooked scenarios, particularly within complex modules like export functions.

Since it appears you haven't tested it yet, I would recommend giving it a try. If you encounter any issues with variables not being resolved correctly, please let us know. This feedback will be essential for us to address any potential gaps in functionality.

Best regards,

Hello Chuck,

Regarding the use of variables with the RVTools Export function in RDM, they should theoretically be supported throughout various functionalities as variables are generally well integrated. However, there might be specific cases where the integration might not be perfect due to overlooked scenarios, particularly within complex modules like export functions.

Since it appears you haven't tested it yet, I would recommend giving it a try. If you encounter any issues with variables not being resolved correctly, please let us know. This feedback will be essential for us to address any potential gaps in functionality.

Do you have any documentation online that specifies what %VARIABLES% are available throughout the RDM program? I cannot find anything with any searches I have performed, so I apologize if I did not look in the right location.

Best regards,

Hello again, the %variables% are related to the environment variables of Windows:

We call this method to resolve the variables:
https://learn.microsoft.com/en-Us/dotnet/api/system.environment.expandenvironmentvariables?view=net-7.0 and here are the defaults:

https://learn.microsoft.com/en-us/windows/deployment/usmt/usmt-recognized-environment-variables

Regards

Thank you, sir.

One thing I noticed is RDM blocks where you can use Variables in some cases.

For instance...





Which within RDM, translates to:


I have to specify the actual directory, so this is useless when the software is being utilizes in a SQL Team Environment where directory structures are not the same for everyone.

Is this something that can be added to the list of fixed issues for the next release?

Hello,
I'm not sure what the source or entry type shown in your screenshot is. Is it an embedded command line (Cmd)? I'm asking because the error (Browse for Folder) you mentioned does not seem to originate from us; it's not a typical warning message.

Hello,
I'm not sure what the source or entry type shown in your screenshot is. Is it an embedded command line (Cmd)? I'm asking because the error (Browse for Folder) you mentioned does not seem to originate from us; it's not a typical warning message.

Good morning, David.

This is from RDM in the RVTools setup. Here is the screen:


When clicking the three ..., that brings up this window:


When clicking in the Folder line to manually input a folder name, you can see when I start typing variables, RDM starts to populate:


When I select the %USERPROFILE%\Desktop population that was automatically available, I get the following error:


So that is where the error is coming from.

This feature does not allow free form typing of the Directory entry.

Last year, I brought up the same issue with the Filename option, and that was implemented in I want to say it was 2023.3.39.0 to allow typing & freeform in the filename.

When I found that issue, you couldn't even type anything in the Filename option itself, so that was a bug that was implemented.

I believe Freeform Directory typing also needs to be allowed in this field as well to suffice when utilizing in a numerous personnel environment.

Hope this helps and is what you were referring to.

Hello,
This is a dialog from a third party. I will report it. You can use the environment variables in the breadcrumb.



Regards

Hello,
This is a dialog from a third party. I will report it. You can use the environment variables in the breadcrumb.



Regards

Thank you for the response, sir. but there is still some confusion. Maybe it's me just not understanding...

So there is no option to either type, manually populate, or select anything in that box that is variable in any way, shape, or form. The same error message comes back:


And when utilizing the entry box you are showing above and clicking the Select box, it does not update anything on the entry, since there is nothing actually selected in the Folder box shown above, where as in your screenshot, it is in the top BreadCrumb box, which does not save as any kind of selection.

Please advise...

Hello,
I think we are talking about the same thing. I have posted the bug report to the third party, and they don't seem to want to fix it:

https://supportcenter.devexpress.com/ticket/details/t1231624/re-feature-request-support-environment-variables-in-address-bar-of-xtraopenfiledialog

I'm not sure I can do anything since I don't have access to this code.

Regards

Hello,
I think we are talking about the same thing. I have posted the bug report to the third party, and they don't seem to want to fix it:

https://supportcenter.devexpress.com/ticket/details/t1231624/re-feature-request-support-environment-variables-in-address-bar-of-xtraopenfiledialog

I'm not sure I can do anything since I don't have access to this code.

Regards

Thank you for at least checking on this.

I saw in your post that you mention it worked in the Breadcrumbs. Maybe if you are utilizing the Web version for RDM Teams, but within the actual RDM Application itself, it does not.

Thanks for the update.