Create Record type from SQL View

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

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