It references function GESZPLN, I assume your customer object is called ZPLN? In that case, ensure you validate the object, window and all screens on it. The "Target entity not found" error is due to Syracuse being unable to load a JSON configuration which is associated to either a screen or window JSON definition located in the "X3_PUB\FOLDERNAME\GEN" subfolder. The only way to correct it is to perform full validations off dictionary elements used by the development. 

Alternatively, change the Global Server values for entities listed below from "Error" to "Debug", which will provide you will a lot more information. Remember to switch them back to "Error" once testing is completed to ensure you don't unnecessarily flood the Syracuse logs :

• Classic > std
• Classic > tracker
• x3Com > adxwhat
• x3Com > gateway
• x3Com > jsRunner

It references function GESZPLN, I assume your customer object is called ZPLN? In that case, ensure you validate the object, window and all screens on it. The "Target entity not found" error is due to Syracuse being unable to load a JSON configuration which is associated to either a screen or window JSON definition located in the "X3_PUB\FOLDERNAME\GEN" subfolder. The only way to correct it is to perform full validations off dictionary elements used by the development. 

Alternatively, change the Global Server values for entities listed below from "Error" to "Debug", which will provide you will a lot more information. Remember to switch them back to "Error" once testing is completed to ensure you don't unnecessarily flood the Syracuse logs :

• Classic > std
• Classic > tracker
• x3Com > adxwhat
• x3Com > gateway
• x3Com > jsRunner

Hi Regard Hulsbos 

Thank you for your assistance.

You're right. I had to do the dictionary validation again after increasing the activity code. Probably something whent wrong the first time. Good to know where the error target entity not found is coming from. 

Interesting point with the increasing of the log level. I assume the logs generated are all located under ...\syracuse\logs. Next time I have such a problem I will try that with the log level increasment. Here  How to increase logging levels for diagnosing issues  I found a description of the different logging settings.

Thanks again and kind regards

Bense

It can also be helpful to use Onerrgo in custom code to find the cause of the problem.