-
Search Results
-
I realise that for lists it’s not possible to create vlookup associations without the extra column workaround due to the item ID not yet being created, but does this logic also carry though for document libraries?
At the point the form loads (editform, not newform as in the case of a list), the ID of the new document is accessible in the form of;http://site/library/Forms/EditForm.aspx?Mode=Upload&CheckInComment=&ID=18&RootFolder=Folder&Source=http%3A%2F%2Fsite%2Flibrary
Is it possible to enable vlookup for editform with mode=upload even though it is a “new” item?
Adam
Hi Alexandar,
First of all, you have a great toolkit!
I’m excited to investigate your latest feature to allow the creation of an item in the vLookup on the new form!My question, do you have the ability to create a new item in the vLookup based upon an item that already listed within the vLookup? i.e Allow the user to select an existing item in the vLookup and create a new item where the columns are automactically copied to the new item. Or, open a dialog box of the items within vLookup and allow the selection of an item from which the columns are copied to a new item?
I hope this makes sense, please message me if you require more clarity or information?
Regards
Rob
Has anyone come up with a way to use a field value from a ‘parent’ DispForm in the rule set for a EditForm?
Im thinking of approaching by requiring the edit form to be a dialog from the Dispform
so am wondering if there is syntax to use in a rule based on a field in the Editform, and compare it to a field value in the parent “Dispform” (note: the field in the DispForm is a supplemental value associated with a Lookup to another list) My goal is to have a rule likeIf {EditformField} greater than or equal to {ParentDispForm.{parentdispfield} then the rule fires.
Has anyone successfully done this?
Im trying set a rule for Editform for a list (On Save) that will set the value of a text field to the concatenation of {fielda}-{ID}. My permutation is I would like the result to be like X-0005, where value in ID is masked with leading zeros in the new field.
I though about setting a rule where if {ID} < 10 have the rule set the value as {Fielda}-000{ID} and another rule if {ID} < 100 and so forth. Unfortunately, cant seem to figure out how to trigger a rule based on the value of {ID}. Anyone run in to this, or have any good idea? (I even tried to anticipate Alexanders’ cleverness by trying {Fielda}-{ID[0000]} like the way {timestamp} works!)
Topic: Using DFFS in Mobile view
Is it possible to use DFFS forms in a mobile view, i.e. on a smartphone or tablet that isn’t using the full resolution browser?
I have a list that is using DFFS. It displays fine on my PC browser of course, as well as on my iPhone when Safari is showing the PC view of the list. However, when I switch to the mobile view I lose all that lovely DFFS functionality, AND the “hidden” SPJSBlog.com field is visible!!
Hope you can help as I really don’t want to be learning a new skill this week!
John
Topic: Workflow Help
So i have setup vLookup to work with DFFS and new form using the _vLookup columns for adding new items to a RMA form when creating new that works great but i also have a Form on our website that gets submitted to a List then i run a workflow to create a new rma item and this workflow also creates equipment in a lookup list.
I was going to use your _vlookupID and_vLookPartentID but i see that this column does not get populated when i create item with a workflow is there anyway to do this?
This code example shows how you can display more information on predecessors in DispForm of a task. By default, only the “Title” field is shown, and as the predecessors are selected from a regular lookup column vLookup cannot be used to show more information.
This code will work for SharePoint 2010 and 2013.
Add this code to the Custom JS textarea:
function showPredesessors(){ var listTitle = "Tasks", pArr = spjs.dffs.beforeProperties.Predecessors, qb = [], cc, q, list, items, res = []; if(pArr.length === 0){ $("#PutPredecessorsHere").html("No items found"); return; } cc = new SP.ClientContext.get_current(); list = cc.get_web().get_lists().getByTitle(listTitle); qb.push("<View Scope='RecursiveAll'><Query>"); qb.push("<Where>"); qb.push("<In>"); qb.push("<FieldRef Name='Title' />"); qb.push("<Values>"); $.each(pArr,function(i,t){ qb.push("<Value Type='Text'>"+t+"</Value>"); }); qb.push("</Values>"); qb.push("</In>"); qb.push("</Where>"); qb.push("</Query></View>"); q = new SP.CamlQuery(); q.set_viewXml(qb.join('')); items = list.getItems(q); cc.load(items); cc.executeQueryAsync( function(sender, args){ var e = items.getEnumerator(); res.push("<table cellpadding='2' cellspacing='0'>"); res.push("<tr>"); res.push("<th valign='top'>Title</th>"); res.push("<th valign='top'>% Complete</th>"); res.push("</tr>"); while(e.moveNext()){ item = e.get_current(); res.push("<tr>"); res.push("<td valign='top'>"+item.get_item("Title")+"</td>"); res.push("<td valign='top'>"+(item.get_item("PercentComplete") !== null ? (item.get_item("PercentComplete") * 100) + " %" : "")+"</td>"); res.push("</tr>"); } res.push("</table>"); $("#PutPredecessorsHere").html(res.join("")); }, function(sender, args){ alert(args.get_message()); } ); }
Then add this code to a “HTML” area in a tab:
<div id="PutPredecessorsHere"></div>
Last step is to add a rule with trigger “Selected tab index” equals the tab index you put the div tag in the previous step. This rule must have the name of the function “showPredesessors” in the “Run these functions / trigger these rules” field.
You will now have a basic table with information on “Title” and “% Complete” for all the predecessors of the current task.
Please note that this code is a basic example, and you will have to use this code as a starting point for your own customization.
Alexander