02-06-2017 02:59 PM
Hi Stefano,
I was able to insert via script. This is what I ran:
INSERT INTO [LocalGov3857].[dbo].[MW_Building_Footprints]
SELECT [BF_FID]
,[PARCEL_VIEW_PFI]
,[LAND_USE_TYPE]
,[FLOOR_LEVEL]
,[FLOOD_RISK]
,[GROUND_ELEVATION_AVERAGE]
,[HEIGHT_AVERAGE]
,[NO_OF_GROUND_FLOORS]
,[NO_ABOVE_GROUND_FLOORS]
,[SOURCE_OF_FOOTPRINT]
,[ACCURACY_OF_FLOOR_LEVEL]
,[DATE_CAPTURED]
,[CAPTURED_BY]
,[DATE_LAST_UPDATED]
,[UPDATED_BY]
,[MI_PRINX]
,[Geometry]
,[Geometry_SPA]
FROM [LocalGov3857].[dbo].[MW_Building_Footprints] where BF_FID = '1006293'
Select * result now gives 2 rows instead of 1 previously
02-06-2017 03:04 PM
Stefano,
PS... Data stored in SQL Server in 3857 and MApp defined in 3857.
See screenshots
Jonny.
02-06-2017 03:08 PM
02-06-2017 03:50 PM
Further to this - i did some more testing:
I have a 'Move point' workflow working - I can move a point geometry and save.
I changed the BLDG workflow (the one giving problems) from GE_MODIFY to GE_MOVE as the action. Now I can move the building footprint and save the new position. It is GE_MODIFY and creating a new geometry that are still giving errors.
Hope this helps in finding a solution.
Jonny.
02-22-2017 02:09 AM
Hey Stefano,
I have updated to M.App Enterprise 16.0.3 patch and used the following action script:
SC.digitize('bagtiel', {commands: ['GE_NEWPOLYGON'], startOnLoad: 'GE_NEWPOLYGON'})
This solved the issue.
Thanks,
Wim
02-22-2017 02:19 PM
Hi Wim,
Can you please share your xml for the NEWPOLYGON part of your workflow as I am still having problems despite updating to SP3. If possible please share all of the form relating to the Geometry creation.
Thanks in advance,
Jonny.
02-24-2017 12:40 AM
Hey Jonny,
Attached is my WorkflowSetting and FormSettings as xml files.
Best Regards,
Wim
03-06-2017 01:00 PM
Hello Jonny,
have you resolved this problem? as i have the same error.
Regards,
Maha
03-08-2017 05:15 PM
Hi Maha,
I was able to create new polygon geometry - however I cannot modify an existing geometry.
Best wishes,
Jonny.