Insert USERID into database as a "CALCULATED" field

[kimhere]

I would like to automatically insert the userid into a "calculated" dbf table useridname field from a web applicatioin.

Previously, I had the dbf table "useridname field" = to a "calculated field" which was set to "API_getusername()".
This works fine for desktop, but not web.
From the web, it stores the server admin login, and what I really need is the __protected__userid.

However, if I set the calculated field = "session.__protected__userid" I get an error message when I try to save the dbf table.

This database is updated simultaneously by several seperate grids, which is why I would like to set it at the field level in the dbf table RATHER THAN doing the work in the "Grid component".

Is there a function that will do this?

I do know how to do this from the Grid Components, but since this field will always be equal to this value, just seems simpler to have it set to a calculated field in the dbf table.

Thanks! Kim

[WendyWelton]

Re: Insert USERID into database as a "CALCULATED" field

You need an Argument to be able to use information from user login. I'm not sure I can 'splain how this would translate exactly, but this might help you (and will at least give you some more topics to research):

I'm on DBF.

argument.png

field.png

[frankbicknell]

Re: Insert USERID into database as a "CALCULATED" field

In the CanInsertRecord event try this
if eval_valid("session.__protected__userid")
e.DataSubmitted.useridfieldname = session.__protected__userid
end if

[kimhere]

Re: Insert USERID into database as a "CALCULATED" field

Thank you both for responding. I am using variations of both your suggestions, but still have not achieved exactly what I was hoping for.

I really just wanted to set this field in the TABLE as a calculated field that would always equal the userid from the web environment. (basically, the equivalent of API_getusername(), as this does not work in the web environment).

Reasons for wanting to set it at the Table level:
1) this table is used in multiple places, saves me from having to insert code into all the different grids calling this table.

2) debugging is an issue when trying to reference the __protected__userid, my applications "bomb" in the working preview and live preview because that variable is not available.

Thank you for your help though, it's great to have access to the knowledge of thousands of people! Kim

[WendyWelton]

Re: Insert USERID into database as a "CALCULATED" field

Kim

I don't believe you can set it in the table as a calculated field. You really will have to do it in each grid. The good news is it really doesn't take long to do that. You can probably just do it in your grids in less time than you'll spend trying to find a way to avoid doing it in the grids!

This is one operation that will not work in the Working or Live Previews, because it's looking for a value that's not present unless you're a logged in user - on your live web site or your localhost. Having it "bomb" there does not mean it doesn't work.

If either of these fails when you try it on your localhost, with a user logged in - post what you've tried to get some more help.

[tayrola]

Re: Insert USERID into database as a "CALCULATED" field

I am not sure if this is what you are trying to do but try this:
1. in your grid make the userID a hidden field so that the user cannot edit it
2. in the OnInitialValueCalculate event put this line:
e.newValues.UserID = a5ws_get_user_from_guid(a5ws_get_guid_from_ulink(session.__protected__ulink))

[frankbicknell]

Re: Insert USERID into database as a "CALCULATED" field

Forgive me if this is obvious... I just insert a value in place of the session.__protected__userid for debugging purposes. ex .DataSubmitted.useridfieldname = "TestData"

[chadbrown]

Re: Insert USERID into database as a "CALCULATED" field

To insert the userid into a table all you have to do is add your field you want to fill with the user id Hide it and put in the caninsert and or canupdate events

datasubmitted.useridfieldname=session.__protected__userid

Sorry missed your reason for not using it like this