Troubleshooting

Known limitations

Conflicts with custom limeobject logic

Solutions that make use of the ability to tap in to the object events such as before_update, might encounter an error depending on the logic implemented.

This package is designed based on limepkg-server-commands, which makes use of unit of work to create and update objects, in a single batch. This means that before the unit of work is committed, nothing is saved in the database.

This can cause issues if the custom logic is interacting with relations, which might not be set until the unit of work is committed. A documented example of this is using before_update in combination with limepkg-communication-flow. In a specific case, this function was used, where it attempts to access person relation before it's created, resulting in an error.

Common Issues

It fails when using lookup

Description

When using lookup, there might occur an error like the one below.

500 Internal Server Error: 
["Lookup '{'email': '[email protected]'}' did not match any limeobject of type 'coworker'.
Lookup must match exactly one record", 'The command was not executed because of previous errors']

Solution

As the error suggests, using lookup for property mapping requires the limeobject searched for to already exist. If it is not certain that the object exists, use Target or find existing limeobjects instead. That way the object is always created if not found.