Overview iOS 12.5. This has been tested manually against our pre functional release test doc. Release notes available here Impact for affected users No impact on Users. Errors Seen (if applicable) — Status All tests have passed. 100% completion. For further updates on all releases, please refer to – http://trust.mobilecaddy.net
When using a Javascript date/time object and passing to a date field an error is thrown.
SUMMARY There was a change in the MC Resource library which enforced a stricter use of Date to Date (rather than allowing Date Time to Date) which can affect existing application code
Import of new MobileCaddy Components fails on Heap Size on certain sandbox/dev boxes
SUMMARY When upgrading the a new set of MobileCaddy Components via the MobileCaddy Component tab and ‘Populate’ process the import does not complete and an Apex Heap size issue is hit
audId not provided – Sync Issue when hitting Table Age Param
SUMMARY On sync calls if the max table age is within the specified range then the sync protection is partially failing and records an error., As expected there isn’t a completed sync being registered on the platform, and applications should function as normal
Permission Set creator – issue with any sObject that have no Owner Id fields
SUMMARY Permissionable objects that do not have an Owner Id did not appear on the Permission Set creator process and do not get added to the created permission set
Permission Set creator – issue with Task Object name field
SUMMARY In the Task object has been mobilised the Permission Set creator fails due to the COMBOBOX field/Name field which does not let the process complete
DV Status change with over 1000 users fails
SUMMARY If a DV status change can affect more than 1000 users the summary list can blow and fail the process
Cache Page Permission Set Naming Issue
SUMMARY If the developer creates the name of the app with two or more underscores then the automatic Cache Page naming does not form the correct value to enter into the created permission set
Create new Mobile Application fails with heap size when large number of tables/fields
SUMMARY When migrating a mobile application and exporting into a new environment this is a synchronous process and if there is a very large number of mobile tables and fields the process can fail due to heap size
CodeFlow: SOQL “IN” and “LIKE” not supported together
SUMMARY The use of “IN” and “LIKE” syntax in smartRead is not available when running in CodeFlow.
- Page 1 of 2
- 1
- 2