Connect Update 15 cannot record a macro with Fill In Enter Data Field

In V8I they record basic macros .bas files.  They use them extensively at the end of a job to update final drawings.

I understand that.  In Connect you can record a macro that creates a BMR file.  It works fine EXCEPT for enter data fields.  This is a simple way for the users to automate tasks.  They do not know VBA and they shouldn't have to.  They make macros on a daily basis and they are not used for weeks on end and so creating VBA projects is not a cost effective solution.  What I really need to know if this is a bug in Connect and if there is a work around

Julie Mascara said:

If you do the record and save it as a VBA or a BMR is does not record the value of the text

It seems to be bug and should be reported, because it was recorded in V8i and should be in CE as well.

Regards,

  Jan

Hi Julie

Edit data fields in v8i don't need to be edit data fields any more... a very long time ago in microstation land  it was not possible to edit text in a cell so edit data fields were used to set up text attributes so you could have editable text inside cells but maintain the  text attributes.  Many  years later I think it was 2000 users could edit text in cells... so IMHO a lot of us stopped using  edit data fields and  just  let it be text in a cell (or even tags) .. and edit the text directly in place  in dgns....and this is still the case in CE .. it however it does depend on your  workflow and what your edit data fields represent  that is why they have been kept for a long time as a legacy feature... but they may well become obsolete in future versions of CE  so it may pay to start learning  ITEMS ( or TEXT)  for new drgs and  amended drgs change over to items or just text 

I know that they have been trying to get rid of Enter Data fields and we have found many issues with them in Connect.  However, removing them right now is not option.  In addition, we use them to maintain consistency in our cells because standards are defined by the customer and cannot vary.  Especially when it comes to font, size and most importantly length because these fields are linked to a database. 

Ok, so you have to keep the Enter Data Fields.

Let's look at the macro part of it. Why are the users recording one each time as a routine part of finalizing the drawings?
Is it because they record the data field edits on one drawing, then replay the macro on multiple drawings afterwards that need the exact same edits?

Jan Šlegr said:

It seems to be bug and should be reported, because it was recorded in V8i and should be in CE as well.

As Jan said, it should be reported to Bentley as a defect. But I wouldn't hold out much hope that it will be fixed anytime soon, if ever.

That leaves you with with creating a custom application, if you want to migrate to MicroStation CONNECT.

A VBA macro or .NET .dll add-in can read and update Enter Data Fields. Either could gather the required text changes through a custom dialog, then apply the updates. It could also be designed in such a way that it applies the same Enter Data Field edits to groups of files so the users don't have to manually run the same edits on each drawing.

This would be something you would have to contract out for if you don't have any programming expertise in your company. That may be a tough sell to management, so you may be looking on staying with V8i SS10 for some time.

A common macro for the users to run is to update the dates and initials in the border of the drawings upon completion of a project location.   We have filed a defect for this.  We have filed some for edfs already where the issue was fixed and then broke again in the next release.   We are looking into changing over from EDFS, but honestly it is way more time consuming to use text.  Too much clicking whereas, if designed properly, edfs are much faster because you never have to leave the keyboard.  Plus the copying and incrementing features. 

A common macro for the users to run is to update the dates and initials in the border of the drawings upon completion of a project location.   We have filed a defect for this.  We have filed some for edfs already where the issue was fixed and then broke again in the next release.   We are looking into changing over from EDFS, but honestly it is way more time consuming to use text.  Too much clicking whereas, if designed properly, edfs are much faster because you never have to leave the keyboard.  Plus the copying and incrementing features.