Here's a quick run through of SharePoint Fields found in 'Edit Properties':
- Name is the filename
- Title is the title of the document that corresponds to Title in the file properties
- SEDocID is the GUID for the item – that is how SharePoint locates everything – do NOT change it
- SERevisionRoot is the GUID for SharePoint to know the revision – do NOT change it
- SERevisedFrom is a GUID for SharePoint to know how to find the document that this one was revised from – do NOT change it
- SE Status is the status (Released, Available) – use Life Cycle Assistant to change it – you should not change it here
- SEStatusUser is the person that last made a change to the status – do NOT change this
- SELastKnownLocation is the last place it was opened and saved – Do NOT change this: SharePoint uses the DocID to locate it if it can’t find it here and then once you open and save, it updates this field
- SELinkData provides a list of the documents that the assembly has in it – typically I look here if someone is opening an assembly and saying that they are not getting the right part – this will show the GUID of the part it is looking for and you can then do properties on the part to see if it is the right GUID – I only see this when someone has deleted a PartA.par and created a new on PartA.par thinking SharePoint uses the name – it does not – it uses the GUID – you have to then do a replace in rev manager – do NOT change this field here
- SERevisionLevel is an internal way for SharePoint to know what rev level – do NOT change this
- SEModelType – do NOT change it - any of the ones that start SE are internal ones used by the system
- Material is the material (you need to have this mapped to SharePoint)
- Document Number should be your part number no extension so 123.par is 123 and this corresponds to the windows properties (can change this here)
- Revision Number is the Revision Number A, B, C or 1, 2, 3 and will use _ or – depending on your settings in options – this corresponds to the windows set up (use Life Cycle Assistant to change this)
No comments:
Post a Comment