difference between Entity Backed records and Process Backed records?

This is about the source of data for your Appian Records. There are 3 possible sources:

• Entity-backed - the data for these comes directly from a database table or view - i.e. a database "entity"
• Process-backed - the data for these comes from Process instances in your Appian application environment 
• Service-backed - the data for these comes from the result of an Expression Rule - which in turn could come from any number of different sources e.g. web services, database tables, or a combination of these

Stewart Burchell 

Stewart Burchell said:

Entity-backed - the data for these comes directly from a database table or view - i.e. a database "entity"

Can it be mapped to a view?How do I map it?

Thanks

A view is seen by Appian as just another database table i.e. tables and views are both classed as entities. You can create an Appian record (or Datastore Entity) from an existing database view in the same way you can for any other database table.

Stewart Burchell 

Thank you for your response.

I was able to map by selecting disable sync and related features and mapping from View, but is that the method recommended by Appian?

What is the difference between mapping using Datastore entity and mapping using recordtype?

spykid said:

is that the method recommended by Appian?

The current method recommended by Appian is to not use views at all, and instead to create Synced Record Types for your various DB Tables and use record type relationships to replace the functionality that a View would have provided.

As has been pointed out to you in your other thread on this subject, you can't point to views with a Synced Record Type (since views can't really be written "to"), so if you MUST use views to query data into appian (one-way), you must still use the older Data Store Entity structure (so in this way, the answer to "is this the recommended method" is "yes", even though it's no longer the preferred implementation).

spykid said:

is that the method recommended by Appian?

The current method recommended by Appian is to not use views at all, and instead to create Synced Record Types for your various DB Tables and use record type relationships to replace the functionality that a View would have provided.

As has been pointed out to you in your other thread on this subject, you can't point to views with a Synced Record Type (since views can't really be written "to"), so if you MUST use views to query data into appian (one-way), you must still use the older Data Store Entity structure (so in this way, the answer to "is this the recommended method" is "yes", even though it's no longer the preferred implementation).

Mike Schmitt 

Thank you for your response.I got it.