This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I want to implement Entity Tracking by tracking the time and user for the creation, update and deletion of an object/record. I have read the following sections in the LightSpeed 4 documentation and they have been very helpful: These sections are very helpful and I enjoy the way this has been built into the LightSpeed framework. I believe this is one up on competing products. However, I see that the UserId properties that we must implement must be of type String. My question is: Is there a way to set up these UserId properties (CreatedBy, UpdatedBy and DeletedBy) as type System.Guid? The reason for this is that my UserId in my application and database is of type Guid? Or are we stuck with only using the String type for these properties? If so, would you consider submitting this as a feature request for future releases? |
|
|
|
|
Yes, this is a good suggestion. It really should allow it to be open rather than locking it down on the interface to a string but allowing the field to be set to anything. Because it would involve a breaking change to IAuditInfoStrategy I have added this in for the 5.0 branch so it will be changed there once we make this available.
|
|
|
|
|
Hey guys, I was thinking about using LS for a new project and this same feature would be a big deal for me. Is there now a way to accomplish this in LS 5? I've taken a look and it appears that IAuditInfoStrategy still returns the user as a string. It would also be preferable for me to return this as a Guid. |
|
|
|
|
Hmm, looks like this didn't make the cut for 5.0 and I didn't update the post to reflect this. You are correct - this is still string based. Ill have a think about what we can do here as its still a good suggestion :)
|
|
|
|
