Skip to main content

How to avoid updates the id’s for signature and implementations when compiling all forms/services?

Author: jens.fyhn@cgi.com (jfyhn)

Then using compile/all I get new Id’s for signature and implementations (fields uspecid uimplid) for some of my services. Only some interface services get this feature and our hundreds of other services leaves these fields unchanged when compiling. When these fields change so much, our version control system have some problem termermining changes, so they always comes up for manual merging when using the version control update. Does anybody have any ideas of some setting in the services or other approaches I can try to have the id’s not changing when there is not done any changing of code?

How to avoid updates the id’s for signature and implementations when compiling all forms/services?

Author: jens.fyhn@cgi.com (jfyhn)

Then using compile/all I get new Id’s for signature and implementations (fields uspecid uimplid) for some of my services. Only some interface services get this feature and our hundreds of other services leaves these fields unchanged when compiling. When these fields change so much, our version control system have some problem termermining changes, so they always comes up for manual merging when using the version control update. Does anybody have any ideas of some setting in the services or other approaches I can try to have the id’s not changing when there is not done any changing of code?

Hi Jens, the ID normally does not change as long as the signature of the object is still the same. If you find any violation of that documented behaviour, you should raise a call to CPWR.


Author: ulrich-merkel (ulrichmerkel@web.de)

How to avoid updates the id’s for signature and implementations when compiling all forms/services?

Author: jens.fyhn@cgi.com (jfyhn)

Then using compile/all I get new Id’s for signature and implementations (fields uspecid uimplid) for some of my services. Only some interface services get this feature and our hundreds of other services leaves these fields unchanged when compiling. When these fields change so much, our version control system have some problem termermining changes, so they always comes up for manual merging when using the version control update. Does anybody have any ideas of some setting in the services or other approaches I can try to have the id’s not changing when there is not done any changing of code?

ulrich-merkel said ... the ID normally does not change as long as the signature of the object is still the same. ...

Could Uobjects that do not have a signature fully managed by the user be the culprits here? I mean as an example those forms without a real signature...for them the Ucompiler AFAIK generates anyway a signature with Execute/Accept/Quit in it... It's just a hint... Ciao, Gianni


Author: gianni (gianni.sandigliano@unifacesolutions.com)

How to avoid updates the id’s for signature and implementations when compiling all forms/services?

Author: jens.fyhn@cgi.com (jfyhn)

Then using compile/all I get new Id’s for signature and implementations (fields uspecid uimplid) for some of my services. Only some interface services get this feature and our hundreds of other services leaves these fields unchanged when compiling. When these fields change so much, our version control system have some problem termermining changes, so they always comes up for manual merging when using the version control update. Does anybody have any ideas of some setting in the services or other approaches I can try to have the id’s not changing when there is not done any changing of code?

It would be great if you could find out under what conditions the id's do and do not change. Maybe we can give more usefull advice when we know that.


Author: Theo Neeskens (tneeskens@itblockz.nl)
Terms & ConditionsAccessibility statement