Konstantin,
Hi. I am reviewing your statement above and we are not sure if you have progress since your last visit to our SAP Community Network.
Let us take your case and review it.
You stated:
1) You modified the Eclipse screen design.
2) You published in production and sync but the device is not showing changes.
What we are stating:
1) Let us assume that you have a prior design (Which is the one showing) loaded in memory or the share. Whenever you publish, there is a likelihood that the old data is still the one stored in SMP.
To fix this: You will need to show a number change (A modification) in your published application. Let us say you have SAPWM-1-0-1.agpz as your application prior file. Then with your new change you still have SAPWM-1-0-1.agpz defined. The actual number did not increment so the system will not detect a change.
So first make sure you have incremented the actual published number (Major, Minor or Modification ApplicationName-Major-Minor-Modification.agpz). Once you have establish that you have published a new modified number in the SMP 3.0 cockpit, you need to go to settings and click Agentry App restart. Make sure you do not choose to restart the SMP Production Server but choose the Cockpit's restart Agentry app server instead. This will force the prior application to be removed and have the new one ready. This is from what we documented under:
This is just used as an example: SAP KBA # 2221583 - JavaBE.ini settings not applied (Example SAP KBA article on why a change is not applied) <-- this is just for reference.
This is theory 1.
2) During your sync with the client and SMP 3.0, the logs (if you enable details) should indicate that there are known definition updates. Does the screen that you modified showed in the logs that it was updated?
There is a chance that during updating or publishing of your application the actual definition was not modified at all. To force an update, you may remove any prior application directory that you used and try to republish, you need to see from the editor that all the definition was republished from scratch. + you need to make sure that the number you used is higher than the prior published application.
This should help and this is theory 2.
3) Another thing that could be happening is that your changes is stated to be for Windows. What if your actual device is using iOS Platform or Android Platform before it is using Windows. So there is a chance that even though you modified Windows platform your client is using the other platform which you did not modify and this is causing what you are seeing on the device.
This can be verified in the actual logs. You need to search what screenset or platform your sync was really using.
To fix this, you may either modify the other platform (iOS or Android) or modify the order of acceptance on the screenset or order screen set ini files (check one of your ini files and determine order) or just check your log files to see what official platform was used during sync.
This is theory 3.
I hope any of our community responses helped you in your endeavor.
Have a great day and update us on what you find out.
Best Regards,
Mark Pe
SAP Platinum Support Engineer