Does anyone know if there is a way to edit a version free variable while the file is checked out by another user? The variable is locked on the data card, but I plan on doing this in the API. Any suggestions?
Does anyone know if there is a way to edit a version free variable while the file is checked out by another user? The variable is locked on the data card, but I plan on doing this in the API. Any suggestions?
David,
I tested using dispatch and it failed on both the "All Versions" and "Latest Versions" version free variables, I would expect API to fail as well.
David
I've tested this as well and it appears a no go.
Thanks guys, I expected so much, but it was worth asking.
***HOLD THE PRESSES GANG***
David, your post piqued my curiosity so I decided to test your theory!
I am writing an API to generate serial numbers in version free variables for a client so I have programmed the data card with version-free variables and run the add-in as the admin user during debugging.
While testing there were 5 files checked out by user "Tim" on pc#2 then I ran the add-in on computer #1 logged in as user "Admin" against those files. The add-in threw the expected errors but updated the version free variables even though the files were checked out on computer #2.
Before:
After while still checked out:
Done: Variables persisted after refreshing the view F5
Then while a different set of 5 files checked out by user "Tim" on pc#2 I also ran the add-in on computer #1 logged in as user "Daniel" against those files. The add-in threw the expected errors but updated the version free variables even though the files were checked out on computer #2.
Add-in produced the same results.
FYI: Tim and Daniel are members of groups with permissions to edit version free variables in all states.
By the way, my post above were the results from using Dispatch and version free variables, not an add-in. I then tried to udpate version free variables using Dispatch tonight, FAIL, variables were not updated.
This is "interesting" news...to say the least.
Tim CEPA
Very interesting.... keep us in the loop on how this goes. I think during my testing the user who had the file checked out did not have permission to edit version free variables, only the admin user running the program did. Do the variable updates stick if the file is not checked in, i.e. if the user selects "undo check out"?
Didn't try that but I will see if I can post the results from that test.
The values persisted even after the undo checkout was executed. The undo checkout even detected the files had been changed and gave a clear warning the files were changed. But the values stuck.
***HOLD THE PRESSES GANG***
David, your post piqued my curiosity so I decided to test your theory!
I am writing an API to generate serial numbers in version free variables for a client so I have programmed the data card with version-free variables and run the add-in as the admin user during debugging.
While testing there were 5 files checked out by user "Tim" on pc#2 then I ran the add-in on computer #1 logged in as user "Admin" against those files. The add-in threw the expected errors but updated the version free variables even though the files were checked out on computer #2.
Before:
After while still checked out:
Done: Variables persisted after refreshing the view F5
Then while a different set of 5 files checked out by user "Tim" on pc#2 I also ran the add-in on computer #1 logged in as user "Daniel" against those files. The add-in threw the expected errors but updated the version free variables even though the files were checked out on computer #2.
Add-in produced the same results.
FYI: Tim and Daniel are members of groups with permissions to edit version free variables in all states.
By the way, my post above were the results from using Dispatch and version free variables, not an add-in. I then tried to udpate version free variables using Dispatch tonight, FAIL, variables were not updated.
This is "interesting" news...to say the least.
Tim CEPA
http://www.equivaq.com