Name: Processing Data with REST APIs in SAP Build Apps to Extend SAP Sales/Service Cloud Version 2
Uploaded: 2026-2-23
Duration: 659 s
Description: Learn how the handover of the currently displayed account in SAP Sales and Service Cloud Version 2 to the extension app works, how to retrieve the corresponding account master data record from the REST API, and how to create a new appointment for this account.

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

This browser is not supported

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Overview

Support Resource

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Scenario Based Assessment

Course Assessment

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

Want to remove this from your Learning List?

Your exclusive access to the SAP Learning Hub, event edition is ready. <link>Start learning now.</link>

Access activated

You can now register for free Live Sessions.

<div><div><div><div><div>Learn how the handover of the currently displayed account in SAP Sales and Service Cloud Version 2 to the extension app works, how to retrieve the corresponding account master data record from the REST API, and how to create a new appointment for this account.</div></div></div></div></div>

Processing Data with REST APIs in SAP Build Apps to Extend SAP Sales/Service Cloud Version 2

This video demonstrates how to exchange data with SAP Sales and Service Cloud version 2 via REST APIs. We'll retrieve account data and create an appointment for the account. Let's begin with the account data retrieval. Enabling data integration is a prerequisite for this. In order to retrieve account data, the technical account ID is passed to the app via a URL parameter. This parameter must be defined in the app. Go to Variables and select Page Parameters. Add a new page parameter. The name entered here will be used in the URL and is case sensitive. In this example, it's account ID with a capital letter I. The data type should match the incoming data as much as possible. The technical account ID is a UUID, so select UUID. This allows the app to retrieve the account ID. The next step is to create a data variable to store the fetched account data. Create a new data variable for the account, which belongs to the account service and give it a meaningful name. In this example, I'll use Selected Account. Select Single Data Record. The required technical ID is the account ID, which is stored in the page parameter Account ID. Expand the logic canvas to see the application logic that SAP Build Apps has automatically created for you to fetch the account data and store it in the selected account data variable. Save the app and return to the User Interface tab. Now you can bind the fields that show account data with their respective variables. Bind the account ID text with its content property to the data variable, selected account, and choose the display ID from its field list. Repeat this process for the account name. Choose the field formatted name and save. Next, bind the contact person drop-down to the contacts contained in the account. Choose the binding icon and select Mapping. Select Data Source and navigate to the Account Data variable. In the field list, look for has Contact Persons, which contains the contact person relations. Drag and drop the contact formatted name to label. This will be the text visible to the users. The value is the technical ID behind the label. Choose the Contact ID field. Save the app and launch the preview. Initially, the app doesn't load an account because there is no account parameter passed to it. Add the account parameter manually to the preview URL. Find a valid account ID with the Browse Real Data feature in the Integrations section. The account fields will populate, and the related contact persons will load from SAP Sales and Service Cloud version 2. That concludes the account data processing. Now we can implement the appointment creation. A data variable is required for the appointment creation. Navigate to the Variables tab. Add a data variable from the appointment service and give it a meaningful name. This variable will be used to fill all required fields. Select the variable type New Data Record. The Logic Canvas contains the function setData variable, which can be used to initialize all relevant fields of the appointment. For example, you can enter a proposal for the appointment's note text. The note is an object itself where the actual content is stored in the notesContent field. Enter text as a placeholder. The user will be able to change it later on. Next, select the account which is also an object structure. The fields displayed here are only relevant when reading appointments. For the creation of an appointment, only the field Account Technical ID is relevant. Bind it to the page parameter Account ID. Choose Save for each level. Lastly, set an initial value for the location of the appointment. This can also be changed by the user later on. The start and end date and time will be defined by the user. For this, a helper variable is needed. Create a page variable that will be used to store the scheduled meeting time. Name it Input Time. Leave the type as text. You can provide an example value that will be shown in bound controls while you're working in SAP Build Apps. Navigate back to the User Interface tab and bind the remaining front-end fields to the variables in the background. The contact person selected in the drop-down should be assigned to the appointment. Bind the drop-down's selected value to the New Appointment Data variable. Choose Primary Contact ID. Next, bind the date and time input fields. The date input field can be bound directly to the appointment's Start Date Time field. A small workaround is needed for the time field. For now, bind the time input field to the page variable, Input Time. The appointment start time will be updated when the user selects Schedule Meeting. Finally, assign the Location Input field to the New Appointments Location field. This concludes the UI and data binding part. The last development task consists of implementing the logic for the Schedule Meeting button. Select the Schedule Meeting button and open the Logic Canvas. The Create Record function builds the core of this logic. Add it to the Logic Canvas and connect it to the Component Tap event. The input properties proposed by SAP Build Apps need to be modified. Change the resource to the Appointment Service. For the record, SAP Build Apps has proposed a blank custom object. Assign the new appointment data variable instead. Select the root node of the variable and save. There are two outputs for the create record function. One output is for the response of the API call. In this example, it's the created appointment. The second output is for potential error messages. Next, add a toast function and an alert function. A toast is a small notification that appears on the screen to give feedback to the user and then disappears. An alert is a dialogue that requires confirmation from the user. Connect the response output to the toast. This will be triggered when the appointment creation is successful. Hence, enter a success message. Then connect the error output to the alert. and bind it to the error message of the CreateRecord function. Now you need to set the start time and end time. To achieve this, insert a SetDataVariable function right after the ComponentTap event and remove the existing connection to the CreateRecord function. Change the target variable to NewAppointment. Next, open the binding editor for the record. So far, the setDataVariable function has only been used to assign an existing record to the variable or create an entirely new object. To update single fields of an existing data variable, a formula can be used. The formula editor can be used to calculate field values. When writing formulas from scratch, the area under the formula field contains helpful features, such as a variable and function library. The formula, pasted here, works as follows. The setKey function can be used to update the value of a field within a data variable. It takes three parameters into account. The variable whose field shall be updated, the name of the field that shall be updated, and the new value. In this case, the new value is calculated using another function's substring, the page variable inputTime, and some static text. The internal format for date and time looks like this. Remember that the start date is already set in the start date time field of new appointment, so only the time part needs to be updated. Substring copies the characters from the start date time field from index 0 to 11. Then the value of the page variable input time is appended, and finally, a static text portion is added to achieve the desired internal date time format. Save the formula for the appointment start date. Now, add a second setData variable flow function to calculate the end date. Both updates could be applied within one flow function. This example uses two separate flow functions for a more detailed view. Assign the new appointment variable. And for the record properties, select formula again. use the set key function to update the field end date time this time the new value is calculated with the add duration function it takes three arguments the initial date time where the duration shall be added a number for the actual duration and the term that specifies the unit of measure for the number in this example the end time is set to two hours after the start time Finally, connect the new step, save the app, and go back to the preview. Edit the URL again so that the app loads a sample account. Choose a contact person and a date. Enter a time. Change the location field or use the pre-populated value and select Schedule Meeting. If everything works correctly, you should see the success toast appearing at the bottom of the screen. You can also view the result in the Connected Cloud system. Navigate to the selected account and open the timeline. Here you can see that the appointment has been created successfully. That concludes the implementation of the appointment creation.