Thank you for the suggestion.
I have changed the group permissions that the user is in, to allow complete rights to edit version free variables, in every state that exists in the db.
But I am still unable to create the EC object that I am trying to create as that user.
Here's a snapshot of the error, when I try to create a new EC as the user.
I've opened permissions on the Folders where the template file is stored, and where the EC will be located, once created.
I've changed to Permit for the Group on all transitions for the EC object.
It seems to be a problem even before the initiate of the object occurs.
But I can't figure out what else to change, or to allow. Any other suggestions would be appreciated
[EDIT Re-read your post] Who are you running this template as? Admin or other user? Can the admin run this file creation without error?
Do you have any API addins running in this vault? I have seen issues with this error when addins modify datacards.
I have no problem running this as admin. I gave the user "DocControl" admin privileges and that account can now create the EC without a problem.
My goal is to allow anyone to create an EC, but not have to give everyone admin permissions.
The only Addin listed is the SWTskAddIn 2012000408
The serial numbers are string.
After setting every possibility to allow the edit of ver free vars, I am able to create a new EC by a person in the All User group, as long as I don't input any data.
Just hit create and let it close and in history it will say it checked in.
I can then edit as many control boxes as I wish without errors.
I have droplist and combo Control Boxes which are variable free.
I changed back the 4 droplist Control Boxes by re-adding in a variable. As long as I choose only those for input the EC will create.
If I touch any other Control Boxes, it won't create as the person in the All Users group.
I still can't find the difference between the DocControl account and the All Users Account that causes the inability to use the Version Free Vars Control Boxes during creation of the EC.
Ok. So it is a permission elevation issue.
You probably already know this, but if not, if you are running the template as the logged in user, make sure the group of the user running the template has permissions in both the folder where the file will be created and workflow state for the following:
State permissions of the initial workflow state where the file will be created:
Folder permissions in the folder where the file will be created:
These have to be sort of "in agreement". Also make sure the files are landing in the workflow you intend them to be.
Last, if your template is set to show the card upon file creation, and if the user clicks "Open File" then this could also be creating an issue.
Let me know if this helps.
I reviewed all of the settings for the group "AllUsers" that the account "epdm01" is in.
For the Folders, I already had the permissions that you showed above. In fact I had more boxes checked.
To be sure nothing is confusing the system, under Assigned Folder Permissions, I removed any folders with "unique" permissions.
Then in the Permissions per Folder tab, I made sure all the suggestions were included in what I have checked.
Next I reviewed the State settings for all workflows. And ensured all of what you showed were checked in every workflow state.
Overkill, but nothing else has worked, so it seemed like a good thing to try.
But I get the same results. As epdm01, I am able to initiate an empty EC, and once I choose create, the EC History shows it checked in.
From there I can edit any Control Boxes.
Maybe the best thing for me to do, is tell people to Create once, then edit.
Turns out it is an issue with version free variables in databases that were upgraded from 2012 to 2013 or 2014.
My VAR said if 2013 or 2014 was a new install, the issue would not exist. There's a SQL fix, that we will run tomorrow morning after backups.
Also they were able to get a SQL query from SolidWorks, that showed all of the "incorrect initial state type" accounts in my db.
Thank you very much for all the suggestions and time you spent on this.
In fact, Tim Webb's picture did not have the following checked box, which you will need for each user to save Card Editor files:
That is incorrect. That checkbox is in the folder permissions which permits users to edit the folder card variables inside Windows Explorer, not in the card editor.