Custom configuration variable creation

Mark Plum said:

MS_DEF

MicroStation configuration variables have the prefix MS_.  That enables you to distinguish them from your custom configuration variables.

Mark Plum said:

I am attempting to have two custom variables (MS_POINTCLOUDDIR and MS_REALITYMESHDIR)

You've created a maintenance problem.  How will you distinguish your variables from MicroStation's variables in, say, a year's time?  Choose a distinct prefix that means something to your project or organisation.  For example, since your organisation is Poe and P Associates, why not PP_POINTCLOUDDIR and PP_REALITYMESHDIR.

OK, no problem with the change of syntax of course (and I understand your point). Still, let me change those variables to PP_POINTCLOUDDIR and PP_REALITYMESHDIR and point those to a particular directory. How do I get Point Cloud> Attach and Reality Mesh> Attach to default to that (those) directory(s) at the workset level? Also, what happened to runmacro.ma (it does not seem to be included with Connect (or has not been updated to this latest edition of MicroStation)?

And yes, John, you have expressed my point quite succinctly. 

Mark, I'd suggest you file an enhancement request on these items. It will require a request for each item individually.

I have never performed such a request, John. Could you lead me in direction?

Open CONNECTION Client and click on the CONNECTION Center, in the browser on the Bentley Cloud Services page at the bottom click on the "New Service Request".  Should be self explanatory from there.

Thank you so much, John. Requests have been made and email confirmations have been received! Have a great rest of your week!

Thank you so much, John. Requests have been made and email confirmations have been received! Have a great rest of your week!