I recently ran into an issue with a client’s system who was using SQL views as entities. This is a powerful capability of Saleslogix but there is one caveat. Make sure that the Saleslogix view is in all caps. When you add the view as an entity, one of the attributes that gets generated is the entity’s “Table Name” property. This will match the underlying case of your SQL view. There is however, Sdata feed code that will assume the table name is all caps. And while SQL is not case sensitive, the Sdata feed is case sensitive so when it goes to look for the entity with the “Table Name” of X when your entity has had it’s “Table Name” property set to x, the Sdata feed will fail.
ABOUT THE AUTHOR
- Why Doesn't the SalesLogix Contact Address Change When the Account Address Changes?
- Creating a Pretty Key like the SalesLogix Ticket ID
- How to make the SalesLogix web insert Contact/Account screen work like the LAN version for Account fields being editable
- Can I use the "Like" operator in a SalesLogix statement??