IMSMA3 script writing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Attribute.SetString("VerifiedBy", "migration"); | Attribute.SetString("VerifiedBy", "migration"); | ||
</pre> | </pre> | ||
The different dates in the table ''fieldreport'' are explained [[Data Entry Form Table | here]]. | |||
==ID number gets decimals==__NOEDITSECTION__ | ==ID number gets decimals==__NOEDITSECTION__ | ||
Especially when using Excel as indata it is common that item ID becomes e.g. Assistance-10.0 which is fixed with 2 Cast.<br> | Especially when using Excel as indata it is common that item ID becomes e.g. Assistance-10.0 which is fixed with 2 Cast.<br> | ||
Revision as of 15:48, 21 January 2015
 |
Changes to scripts in 6.0 are outlined in Script changes 6.0. |
Workarounds
 |
ICR-114: The update query in Multi-select CDFs needs to be added as a Data.RunSQLStatement if any of the fields that are imported are multi-select. |
Approval information is not set
The approval function was changed in 5.08.02 and Approved by and Approved date needs to be set in the script in Pojo Fieldreport.
Attribute.SetDate("ReportVerifiedDate", Data.CurrentDate());
Attribute.SetString("VerifiedBy", "migration");
The different dates in the table fieldreport are explained here.
ID number gets decimals
Especially when using Excel as indata it is common that item ID becomes e.g. Assistance-10.0 which is fixed with 2 Cast.
Attribute.SetString("LocalId", "Assistance-" & Cast.String(Cast.Int(Row.GetAttribute("ID"))));
Limitations
Unfortunately it is still not possible to use the following in scripts:
- greater than (>)
- less than (<)
- LIKE (e.g. Eriks* or Eriks%)