Hi,In our company we created custom location for OBD standards. In WorkSets we added path to our custom Dataset. Everything works fine except DataGroup Catalogs and System included in Dataset. In Definition editor all roots are still directed to our local drive where all variables are direct corectly to our custom drive. Is that our mistake and we missed up something in config files or should we add some variables to direct DataGroups to our network drive? We want them to be in our custom dataset on the Organization level.A.
What I've found is that with OBD, it's not ideal to use a custom location for core datagroup (DG) files, the ones that sit "C:\Program files..." by default. It's better to add your company's DG data in addition to Bentley's core DG data. There are a lot of hard coded in OBD's configuration that requires some DG files to be in the right places.
Hello Adrian,
I agree with Tuan, The definitions are always system level which comes from program files. Its better not to edit them or reroute to other location, The custom definitions can be put under dataset, organization,worksetset level and then they can be fetched. The highlighted items are all coming from System level and they are sometimes hardcoded to be picked from that location only.
Hope this helps you.
Regards,Alifur
The OBD Datagroup definition files (XSDs), we have two vertical folder structures one is 'C:\Program Files\Bentley\OpenBuildings CONNECT Edition\OpenBuildingsDesigner\DataGroupSystem' and other one is "C:\ProgramData\Bentley\OpenBuildings CONNECT Edition\Configuration\Datasets\Dataset_XY\DataGroupSystem". Almost all delivered definition files (XSDs) have been intentionally kept and configured from program files location. Since this is your custom workstation, it would be advisable to create new definition files within custom location and keep delivered XSDs as it is.
Thanks & Regards, AR