'Update Features' activity not working after GXMobile update 5.6
There is a critical issue that is preventing the 'Update Features' task from working properly after the recent update to Mobile 5.6 - the issue is the 'update features task' only seems to write the updates for certain fields and not others - I have tested this issue on multiple Feature Services/Fields and the issue persists. I am stumped as to why certain fields are updated in the feature service and not others (all fields are editable). Moreover:
- This issue only happens when running the workflow in Geocortex Go v5.6 in 'Online' mode. Everything worked fine prior to the update.
- When running the workflow in an Offline Map Area (in v5.6) and sending changes, everything works fine.
- The workflow runs fine when run in the HTML5 viewer.
I have attached a sample workflow (Test.json) that demonstrates the issue along with a screenshot of the Feature Service REST Endpoint. Some notes:
- In this sample, the 'Update Features' tasks writes updates back to the feature layer for the 'Busi_Name' field but not to the 'Busi_LegalName'. Both fields have identical settings/parameters. 'Busi_Name' is the Display Field for the feature layer, if that makes any difference.
- Since I only want to updates attributes - I have set the Query 'return geometry' to false. However, the issue persists regardless of returning geometry or not.
I would appreciate your help on this issue - we were just about to enter final testing for our production app for the 2020 Halton Region Employment Survey, but are unable to proceed due to this issue. @Amanda Frech? @Cam Carmichael? @Cam Carmichael? @Stefan Schweigert?
-
Hi Arjun
We're on it - will see if we can reproduce based on the sample you've sent and if not reach out directly for more details.
We'll update this space with a resolution if/when we sort it out.
0 -
@Cam Carmichael? Appreciate the confirmation!
0 -
@Arjun Rattan? Just a quick follow up. We have reproduced this issue in house and investigated and confirmed that you've found a bug - which we will fix for our 5.7 release (scheduled for early June).
In the meantime - we think we have a workaround - which we are testing and will provide details on shortly.
Stay tuned.
0 -
@Cam Carmichael? Appreciate the update and the quick turnaround on investigating this issue. Hopefully the workaround won't involve major changes to existing workflows, particularly if this will be a temporary fix till 5.7 is released. We are intending not to update any versions of Go/GXM/Workflow once we have built and tested a stable app and go-live, specifically to avoid situations like this where new bugs could affect field operations. We were originally slated to go-live for May 1, 2020 but due to Covid-19 our Go-live date may be pushed back a few weeks.
0 -
@Arjun Rattan? Hi again. The proposed workaround would, indeed, require significant refactor to your workflow. Based on your message above, and on the fact that others may encounter this same issue (and not receive special instructions for how to workaround) I've asked the team to investigate the cause and find a fix for this issue. Based on their findings we will consider a service release to correct this issue for everyone. Stay tuned - we're on it - I'll update this space with more info when I have it.
0 -
@Cam Carmichael? That sounds awesome, appreciate your communication and keeping me updated.
0 -
@Arjun Rattan? We have identified the culprit - indeed an issue associated with the 5.6 release - and we've put together a 'fix' which is currently being tested. If all goes well - we'll push to the app stores on Monday and - after a review process - we should be able to publish a 5.6.1 build which fixes this. No guarantee - but hopefully you'll have an updated build by mid-next week.
0 -
@Cam Carmichael? Thanks for the update, and we appreciate your team prioritising fixing this issue. I'm sure other organizations appreciate it as well. Mid-next week works for us as our go-live has been pushed back to late May. This should give us enough time for final testing before launch and go-live.
0 -
@Arjun Rattan? No problem! Thank you for bringing it to our attention!
I'm happy to report that we have fixed the issue and are releasing a 5.6.1 maintenance release build.
5.6.1 builds went to the App Stores late yesterday and today we have updated our SaaS Designer and put up new on-prem installers.
Please update and let me know how it goes.
0 -
@Cam Carmichael? I did a quick test and 5.6.1 appears to have fixed the issue! Thanks again for prioritizing a fix.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
10 kommentarer