Regarding generation of Xcode projects

[javi09]

Hello community,

The following question comes to me regarding the regeneration of projects in case of updates on the design of the app:

The Assistant includes a button "Regenerate proxy clases" that it worked fine to me when I changed fields on the Data Model that is the base of the OData service that I'm using, but in other cases it was not the same . Example case: A change on the GW Service Builder with new properties added to Entity, at the moment of regenerate proxy classes on Xcode, some errors in code appeared "Entity has no member xxx", "properties without default value"(especially if is a primary key change).

So could someone recommend me if, Is it a good practice to generate the Xcode project again? And copy/paste the logic written in the previous project, instead of regenerating and solving code errors?

Thanks, Javier

[AlexGiguere · Accepted solution]

Hi Javier, for us we have found this functionality very buggy,

I prefer using the CLI, regenerates my proxy classes then cut & paste them inside my project

here is the CLI that I used

sapcpsdk-proxygenerator -m ./sap-metadata.xml -s ODataService -dio -internal -v

in this example my file is named sap-metadata.xml

and the generated service will be named ODataService

you don't need to have your proxy classes exposed as public, that is why used the -internal

Alex

[javi09 · Accepted solution]

Thanks a lot Alex,

I am more accustomed to use the assistant (so far), but it is true some functionalities leave much to be desired, CLI is better. I think these command-line tools Proxy Class Generator and ILOData will be quite helpful in the future.

Regards, Javier