Create Record type from SQL View

Just choose database as the source but don't enable data sync.

docs.appian.com/.../configure-record-data-source.html 

Hello [mention:734d485eba7242aeab9bb03aafa409b0:e9ed411860ed4f2ba0265705b8793d05] 
While creating record type select source type as Database
Make sure to select disabled sync and related feature.
Select view from respective data store.

https://docs.appian.com/suite/help/24.1/Create_a_Record_Type.html

hi [mention:734d485eba7242aeab9bb03aafa409b0:e9ed411860ed4f2ba0265705b8793d05]   go to appian designer, create a new record type, once record is created you will find the below UI : then click on tell us about your data

Then click on database: 

After that, select disable data sync option and click on next,: If you enable and move forward you will be unable to find your view, view will not be found seen when data sync is enabled

The you can browse or search your view name and finish creating the record type:

1.  As far I understand , if we create with disable sync feature , it may not be of that useful and performance efficient as indirectly it queries the data from table/view, as nothing is cached.

2. As view is in memory that's the reason they might have disabled the sync feature for this.

3. I would suggest better to create view using record types with sync enabled, instead of querying the view using record. Again up to your use case, just check which is better suits you.

4. Try checking the performance of all the three, querying the record type built on view with disable sync, querying the view using query entity, build view using record types with enable sync.

Just curious to hear the feedback of #4 for your use case.

For what it's worth I think it's a "horses for courses" debate. There's nothing inherently evil about Views (we got along with them fine for decades!). The performance red flag might be a false flag - a View doesn't necessarily equate to "poor performance" (a badly written View and/or Views that use tables that are poorly indexed might perform badly of course - but they might not!).

Another way of looking at this is that the whole purpose of Record Relationships in Appian is to emulate "joining tables in a database" and what are Views if not two or more tables joined together so that normalized data is brought together in one convenient place for use?

So (in short) you could do the following;

• examine the View that you're wanting to bring into Appian as a Record
• create Records for each of the tables that the View is composed of
• add the relevant relationships between those Records
• add in any derived (custom) fields
• use the Record Relationships to get the data that the View currently provides and (if possible - if it's not being used elsewhere) deprecate your View