M.App Enterprise Discussions

Discuss topics with other M.App Enterprise Product pioneers and experts to get the most out of it.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Occasional Visitor
Posts: 1
Registered: 2 weeks ago

Edit Geometry Bug MAE 16.6.287.3

An error of no feature selected pops up when edit geometry action is selected. This occurs even though there exists a valid geometry in the DB. 

Also, when exit edit geometry button is selected, the user isn't referred back to the workflow form. Note, this doesn't affect the older version of MAE as I tested or tried to replicate this on both vesrions. 

 

See video attached.

Highlighted
Technical Evangelist
Posts: 735
Registered: ‎11-12-2015

Re: Edit Geometry Bug MAE 16.6.287.3

Hi Aki007,

 

I have moved your post from 'General Discussions' to M.App Enterprise discussions to get you specific feed back.

 

I cant see from your video where you have selected a geometry to be edited. Given the prompt message you recieve that is good thing to confirm. In quick testing here, I was able to use 'Edit Geometry' tool in MAE 16.6.287.3 without getting this prompt message.

 

Unfortunately, from the video and your description there isn't enough information to draw more conclusion or put in advice than this. At least for me it leaves too many questions to narrow focus at this point. You might include additional information here, such as your 'Edit Geometry' Action definition in the .xml. You may wish to submit a Support Ticket to get further investigation.

Highlighted
Staff
Posts: 1,088
Registered: ‎10-18-2015

Re: Edit Geometry Bug MAE 16.6.287.3

please check the edit action definition carefully on this tutorial:

https://community.hexagongeospatial.com/t5/M-App-Enterprise-Tutorials/Javascript-API-in-Desktop-M-Ap...

 

you must provide the id of the feature to be captured in to the SC.digitize method.

Another thing to check is the data type for the ID field. In some older versions there was no type checking and sometimes you could get it working anyway. I would also check the width of the number, there are limitations in the .NET framework for some DB vendors.

Stefano Turcato
Presale Engineer
Hexagon Geospatial