nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding entries to the "Ratings" table

Matthew Charters

We'd like to add a new constituent rating to use with our application, but when we tried adding a table value to the “Ratings” table using the Data Integration we're getting an error saying that particular table is read only.

Is that really the case? We are able to create a rating source without any issues. If this is expected behaviour, is there some other way to create a custom constituent rating that we can then add to constituents via the CreateConstituentRating endpoint?

Find more posts tagged with

Comments

Brian Riesen

@Matthew Charters
Hi Matthew - Are you still receiving the Read Only error or were you able to find another way to create a custom rating that meets your needs?

Matthew Charters

@Brian Riesen we're still getting the Read Only error. I haven't found any other way to create a custom rating so if there is one, would love to hear suggestions you might have.

In the meantime we are creating a custom field on the constituent where we'll store our rating instead, but it would be nice to create the rating where a user might expect to see it.

Anthony Gallo

@Matthew Charters
This is the current correct behavior. The 5 Read-only code tables are TributeType, PhoneTypes, GiftSizeAnalysisCodes, Ratings, Country, because they have extra non-basic properties that need special handling. In the case of ratings, that special logic is around the data type: text, number, datetime, currency, yesno, and table.

We do not currently have any API endpoint to create rating types like this, and it would need special endpoints. The new code tables area does allow the editing and creation of these types, but that API has not yet added this functionality.