Question

Field Level Auditing requirement for 100 fields

Our client has requirements where they need to log the field changes. The number of fields are around 100 and most will be committed along the case flow ,not at once.

Is there any other optimized approach other than Field Level Auditing.

Correct Answer
October 31, 2018 - 5:38am

This seems to be exactly what Field Level Auditing is for.  What are the reasons for looking for an alternative solution?

Comments

Keep up to date on this post and subscribe to comments

October 31, 2018 - 5:38am

This seems to be exactly what Field Level Auditing is for.  What are the reasons for looking for an alternative solution?

November 1, 2018 - 3:06am
Response to Marc Alderman

Hey Marc,

This seems to be exactly what Field Level Auditing is for. 
[Abhishek] I have used this for key fields in my previous implementations. But my current requirement wants to use the same to Log everything in the case(50 > properties). I think it will be a performance hit for the application for each save\commit.Any inputs?

What are the reasons for looking for an alternative solution?
[Abhishek] Keeping in Performance in mind, i was thinking if there could be another way to implement the same.