👉

Did you like how we did? Rate your experience!

Rated 4.5 out of 5 stars by our customers 561

Award-winning PDF software

review-platform review-platform review-platform review-platform review-platform

Video instructions and help with filling out and completing Dd 1750

Instructions and Help about Dd 1750

True," hey and welcome to another episode of SAP Tech Points. Today we're going to continue with our end-to-end sample, and we're going to build the Adverticats app with the SAP BTP SDK for iOS. We're taking the UI Kit-based approach, so this is Part One. We're going to build the first screen with a list of the available advocates. So let's get started. So, what you see here is the Advocates app within SAP Mobile Services. I've already created the App Cloud application configuration, and this is just the basic setup for the Advocates app. I've also enabled offline access and already created the destination to the Advocate service, in this case v2, because I want to use offline OData and no authentication. If we ping that, we should see a successful ping. Next, I have the SAP BTP SDK assistant for iOS, and you can see I've already connected the assistant with my Mobile Services account. Let's say create new. Here, I can choose to save or reuse an existing application. I already have this application defined, so I select that and proceed. I select the account, do a quick log on, and here I can see the advocates already listed. I say next, and here I can create the Xcode project. I'll just call this Advocate app and save it on the desktop. Clicking next, I leave the proxy classes as is, and here I indicate that I want to have the onboarding as well as the master detail screens for my destinations. Finally, I say finish. Now, what happens is the assistant uses the Xcode CLI to create the Xcode project, stop, and insert all the generated code. For example, the proxy classes in the OData service layer. It will fetch the metadata document from the Advocate service and...