Service back records

If you want to move to Service backed records , For your case you need to consider the below things.

Ramya D said:

To truncate the existing data I am thinking to use delete records.

I don't think Delete Records is the right option . Write a store procedure which truncates the data . (Delete records works like Delete statement in SQL ,Primary key is not going to start from 1).  

You need to do Full Sync after , So Make sure timing of Full Sync (Yogi's Suggestion) comes after Schedular .

Ramya D said:

Do we need to hit the API twice? once to check if it’s success and second to populate the record?

There is a limitation on API call for data syncing , You can sync Only 1000 rows for one hit , So you need to process it in batches if data is heavy. Refer Documentation about this. 

 https://docs.appian.com/suite/help/23.1/generate-web-api.html#overview

Ramya D said:

Also, Unsure how serviceback record handles if integration fails.

I think this you can handle it in Web Api expression itself Based  on error codes. 

If you want to move to Service backed records , For your case you need to consider the below things.

Ramya D said:

To truncate the existing data I am thinking to use delete records.

I don't think Delete Records is the right option . Write a store procedure which truncates the data . (Delete records works like Delete statement in SQL ,Primary key is not going to start from 1).  

You need to do Full Sync after , So Make sure timing of Full Sync (Yogi's Suggestion) comes after Schedular .

Ramya D said:

Do we need to hit the API twice? once to check if it’s success and second to populate the record?

There is a limitation on API call for data syncing , You can sync Only 1000 rows for one hit , So you need to process it in batches if data is heavy. Refer Documentation about this. 

 https://docs.appian.com/suite/help/23.1/generate-web-api.html#overview

Ramya D said:

Also, Unsure how serviceback record handles if integration fails.

I think this you can handle it in Web Api expression itself Based  on error codes. 

Hello Yogi Patel .Thanks for the reply.It really helps.

Also,Just to confirm on the below queries as well.

1.Assuming Purge will happen upon success ,in case of error purge wont happen and exixsting data remains as is.

2.Do we get any error alert in case of error scenario that we usually get if something break/fails in appian. i tried to look where to configure but could not see the option.

3.Will the service back records works simlilar to the DB backed records with respective to relationships?

Skip failed syncs

Alert when Sync failed

Do a small POC and validate your requirements.

I haven't used service-based Records with a scheduler. We are using this scheduler for entity-backed records.

Thanks Yogi Patel Sure .I will check .