One of the biggest complaints I've noticed over the years from those of us who look after the day to day running of CAD packages is the way in which packages, at times, seems to go off in their own direction to the detriment of others. Imaging the insanity of having 2 packages from the same firms that operate in 2 very different ways.
This is what we now face with OBD vs MicroStation and who knows what other products.
While I appreciate that the introduction of Workset and Workspace is a help for some, for others it's not necessary and not required and something we have been working with Bentley to resolve.
You could have knocked me down with a feather when I began my Connect OBD build, which should be a piece of cake, only to get some strange exception errors. A bit of trial and error and it seemed to be something to do with not wanting to use Workset and Workspace in the OBD build. Something I would have thought should not be an issue after working through my base MicroStation build. SR logged and now I'm being told you CAN'T run OBD Connect without some sort of Workset and Workspace.
'It is not possible use OBD CE without WorkSpace and Workset.'
This from Bentley Tech Support.
WHY? Why would you make the customisation of the 2 products so different? WHY, would you remove the biggest selling tool Bentley software has ever had in my eyes. The ability to work with the product configs to make it run how I need it to.
Where next?
Hi Sean,
For others reference this is being discussed in https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/195687/why-are-workspace-and-workset-a-compulsory-requirement
Marc