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

chetany

A Score Level 1

over 9 years ago

Hi, I am using the a!recordIdentifier() function to get the record identifier. My record-type is service-backed.
I am ensuring that the source Expression rule of the service backed record returns datasubset with identifiers.

I want to be able to post a event on the tempoo using the Record tag. (which requires recordIdentifier).
But, I am not able to get the record identifier. When the message is posted on to the tempo feed, it shows the Record tag as "Not Available"

Previously, my record type was entity backed and I was able to view the Record tag when I posted to the tempo.
But, no luck with service backed record.
Any idea what I am missing?

Discussion posts and replies are publicly visible

Parents

0 codys over 9 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 codys over 9 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data