Check our Case Studies for examples of how we've helped various companies realise the benefits of Customer Engagement...
Using Value Type Outputs with Actions
At OA Systems our team are always looking for smart ways to solve technical problems, here is an example of how we get this done.
Actions are not a new term in CRM, we use them a lot.
However, I recently encountered an interesting error with one.
I had an Action to retrieve the birthday from a contact, so I created an output parameter as Datetime type:
As you can see, I set “required” as false, because the birthday is not a mandatory field on the Contact.
As some contacts did not have a birthday set, effectively a “null” field when I used this Action an error happened, I also added a value check before using the Action output:
From this error, I can see CRM set the output to the initial value of the Datetime type (datetime.min) if the birthday is empty. Therefore, it always passes the “contains data” check.
I must add one more output parameter: “getBirthday”. This output parameter will check if the contact has a birthday greater than datetime.min.
Before using the birthday output, I have to to check if the “getBirthday” is true.
Now the error has been resolved.
In conclusion, the Action sets a default value to all the “Value Type” output parameters. The Value Types output parameters include: Boolean, Datetime, Decimal, Float and Integer.
For more information connect with the team at OA Systems
The OA Systems development team has a really detailed understanding of every layer of our businessAyla Hutton, Technology and Projects Manager at Safety ‘n Action
Level 1/95 Ascot Avenue
We are always looking for people who are excellent and passionate at what they do to join our team. If this sounds like you then we'd love to hear from you!