Hi, I am using the a!recordIdentifier() function to get the record identifier. M

Maybe there's an issue with the ID you're passing. According to the documentation forum.appian.com/.../System_Functions.html for service-backed records, record ID is the value returned to the ID field of the DataSubset produced by the record's source expression.

I've always had to use tostring with the id when using service backed records to get this to work

Hi rodgraham. I applied toString to identifier while using a!torecordIdentifier(). It now displays the record tag. Thanks a lot!

We are encountering the same issue with our rule-backed record. However because we had to convert an existing entity-backed record to a rule-backed record due to an Appian performance issue, we already have existing News entries with stored recordidentifiers of type Integer. Eduardo, is there a better workaround to this issue that can also apply to existing entries?

@codys, @Eduardo, are rule-backed records better at performance than entity-backed records? I just want to confirm my understanding. I think service-backed records will be better at performance than entity-backed records. Suppose you are using a!queryEntity() to get the datasubset in your rule-backed record(service-backed record). You have the flexibility to only retrieve only the columns you desire rather than retrieving all the columns (attributes). Besides you can always apply rule-based facets dynamically to rule-backed records. One thing is sure - Service backed records allow more flexibility and control while we are configuring them. But are they better at performance than entity-backed records?

@chetany, I cannot speak in general terms, but for our use case, service-backed records offered an order of magnitude performance improvement because of the flexibility with default filters for record-level security. Now instead of applying an IN filter with 1900 viewer group IDs for admins and auditors, we can escape the filter entirely for those users. If a service-backed record enables a more intelligent filter design for your record then you will see performance improvements in cases like this.