Generally speaking, you shouldn’t ever need to record the id from a User, or really any thing, since you can simply store the actual User thing in a user data type on any other thing.
That being said, the id is a text string, so change IDUWEB to a text type and you’ll be set.
Ok, yes just did that, and display 32 digits now. TKS
So, hmm i m doing this ID records in order to retreive users’ records in a table shared by all users…
I have to deal with a situation when user A is required - as an extra work - to send some data (lets say a report) on behalf of user B and/or C…etc…
All users Data falling in the same Table…
In that case I guess that recording the datas “belonging” to its original user would imply recording built-in Id of user B… havent got here yet. but will see if that could possibly work.
…or do you know of another way arround the Built-in ID in that send on behalf of + retreiving each an everyone datas<-related->owners ?
The benefit here is that you don’t have to perform searches downstream to find the user, it is just there for you to access when you access the rapser.
I ll test that, though I guess Current user would refer to some “user’s name or pseudo”…
1 thing I d want to avoid is working with users id names…that can change in the time for whatever reason,
breaking the tracking of historical recording if so…number does not pause this problem.
I ll give it an eyes and see how it can be applied in that case, tks