Dear Wilfrid,
thank you for your response.
Instead of writing the base64 string to a LONGSTRING on a save event we decided to do so on setAttributeValue event.
When exporting on save we had the problem that it was possible to e.g. change a path to an external image, not saving the model and exporting without creating the base64 string.
To make the solution work on setAttributeValue we are setting a “boolean" global variable on StartADLImport to 1 – so that we know we are about to import. And we set it back to 0 on EndADLImport.
Checking that variable on setAttributeValue is giving us the chance to avoid unwanted override actions when an import is running.
But we ran into another problem:
We decided to use CLOBs to save the base64 code of the images. It seems that CLOBs are not supported anymore by the ADO environment:
When we create a CLOB attribute and export and import our library the CLOB attribute is changed to a LONGSTRING attribute...
The problem is that the LONGSTRING attribute does not take enough characters to save an entire base64 encoded image.
(By the way we took a very small image that was of ~25 KB size not encoded)
We would like to ask you again for your advice – do you have an idea how to solve our problem?
Sincerely the e-GPM Team at WPS.