I don’t know why, but for some reason that action doesn’t work as expected with the “Level” field. The workflow would get stuck at the wait action every single time and never come out of it (even when the level changed to 1).
Since the “Current Item” variable in my workflow included a “Level” field (indicates the check-in status of an item), I initially thought I could use the Wait for Field Change in Current Item action and wait for that field to change to “1.” I needed a way to make the workflow wait for the initial check-in to occur so all the data would be present that was needed by the workflow. The caveat is SharePoint runs the workflow immediately upon upload and doesn’t wait for an initial check-in to occur (which is a separate step if your document library has required metadata fields that must be filled out). I was working on a SharePoint 2013 workflow the other day and turned on the “Start workflow automatically when an item is created” setting so my workflow would run whenever a document was uploaded into a document library. Making a SharePoint 2013 Workflow Wait for Document Check-In the 'Name' property of each file in the collection. exception if I hadn't used the nested Includes above to load This line would throw a 'property or field not initialized' Var fileLooper = subfolder.get_files().getEnumerator() Var subfolder = folderLooper.get_current() Var folderLooper = subfolders.getEnumerator() and loads the 'Name' property of each file in the 'Files'Ĭtx.load(subfolders, 'Include(Name, Files.Include(Name))') 'Name' and 'Files' properties of each SP.Folder object in Here are the nested "Include" clauses. Var folder = ctx.get_web().getFolderByServerRelativeUrl('/server-relative-path/to/folder')
Var ctx = SP.ClientContext.get_current() Since it took me a while to find the syntax for it, I figured I’d save others the trouble and just put it right here. Recently I needed to load properties two levels deep when using the JSOM (JavaScript Object Model) API in SharePoint 2013.
0 kommentar(er)
