Tempo News Feed Updation

RE: Tempo News Feed Updation

Sathya Srinivasan — Tue, 17 Jan 2017 15:15:50 GMT

Okay, from what I understand here, the ID is not really unique if it can change. The approach for your architecture would be better if you used a unique ID for this user (not necessarily this ID, but something that would stay the same) for the Record Tags.

RE: Tempo News Feed Updation

yogeshd149 — Tue, 17 Jan 2017 10:54:34 GMT

Hi Eveyone, thanks for the replies.
@Sathya: Unique id we are referring here is not primary key but a unique id assigned to a employee of the organisation. The same is used for display purpose which while clicking on it will take us to the particular record on NEWS feed. Now as per business requirement that unique employee id can change. So we are planning to change the historical data as well in business DB, but on news feed still it will show the old id.Now as per the replies, it is evident that news feed data cannot be changed.
So we are planning to change the display identifier. Please let us know if this approach is correct or is there any other work around

RE: Tempo News Feed Updation

Karthik — Tue, 17 Jan 2017 10:28:32 GMT

Build a view on the specific table and have sysguid as one of the extra column n pk. This way it will be reflecting new data n doesn't require to update the news feed, btw, I don't think we can update already posted news feed

RE: Tempo News Feed Updation

mathieud — Mon, 16 Jan 2017 18:57:58 GMT

New feed entry cannot be updated.

RE: Tempo News Feed Updation

ChristineLHutchison — Mon, 16 Jan 2017 17:20:29 GMT

The meta data for news is in the primary datastore, that it is not recommended to access.
Would it be possible to alter the table or create a view that will create/house a true, unchanging, unique id to avoid this issue?
Maybe some transaction level table that stores orig id and new id, then link to main table via view to populate/keep id consistent.

RE: Tempo News Feed Updation

Sathya Srinivasan — Mon, 16 Jan 2017 17:03:12 GMT

Why are the ID's getting modified? Typically, an Entity model should enforce a unique key to identify the entity and stay the same for the lifespan of the entity (especially in situations where the entity can be referenced and used in other places). Changing the ID is breaking a fundamental law of maintaining integrity in your entity model. So, I'd like to understand what is the use case for the ID to change. Probably, it would help figure out how to address this issue.