Forum Replies Created
-
Posts
-
Hi,
We have sorted this out by email, but for others experiencing the same:As you have found, this behavior occurs when you have not configured the form with DFFS yet, and therefore no configuration is found. The overlay will time out with “this took forever”, but you can scroll down to the bottom of the form to find the “Enhanced with DFFS” button. When you have saved the configuration, the overlay should behave properly.
Hope this helps,
AlexanderHi,
I cannot think of any other method than to set up a rule for a selection of fields that you want them to change, use the trigger “is changed from initial value” and call “showTheSaveBtn” in the “Run these functions.Then add this to the Custom JS:
// Hide initially spjs.dffs.toggleSaveBtn(false); // This function triggers on a rule function showTheSaveBtn(){ spjs.dffs.toggleSaveBtn(true); }Alexander
Hit F12 and look at the console for errors. Also check the “Document mode” and the “User agent string”. You may also check to see whether or not you have the site in “Compatibility mode” – if it is on, switch it off and the other way around.
There are other reporting the same issue and it might be due to a timing issue and possibly that the user clicks two times on the calendar icon.
Alexander
It looks like this is the datepicker window that resides. Which version of SharePoint are you using, and what browser are you using?
Alexander
This is possible. Add this code to the custon JS in the Misc tab:
(function(){ var b = [""]; b.push("<td class='ms-toolbar' nowrap='nowrap'>"); b.push("<input type='button' class='ms-ButtonHeightWidth' value='Final save' onclick='finalSave();' />"); b.push("</td>"); b.push("<td class='ms-separator'> </td>"); $("input[id$=diidIOSaveItem]:last").parents("table:first").parents("td:first").before(b.join("")); })(); function finalSave(){ setFieldValue("YourFieldInternalName","Completed"); $("input[id$=diidIOSaveItem]:last").click(); }You must change the “YourFieldInternalName” in the finalSave function.
Alexander
Hi David,
I have tried to set up a site and list as you describe, but I cannot recreate the issue. Can you email me some screenshots of your setup so I can look into it?You find my email in the “About me” tab in the top of the page.
Best regards,
AlexanderIf you use the debug option to make the original input fields visible – does this give you any clues?
Could it be that you have a rule in DFFS that strips away your value?
Alexander
Sorry for the delay. This is not possible without custom making a dialog. In the example you have an ok or cancel button, and you can use them to set a field value for OK and another for Cancel. Here is an example on how to set the value:
setFieldValue("FieldNameHere","value you want to set");Hope this helps,
AlexanderEnsure you have put the license code above the DFFS_backend.min.js in the “DFFS_backend_CEWP.js.aspx”, and above the DFFS_frontend_min.js in the file “DFFS_frontend_CEWP.js.aspx”.
Refer the installation manual section 2.3.3. and 2.3.4: https://files.spjsworks.com/files/DynamicFormsForSharePoint/v4/InstallationManual/How%20to%20set%20up%20DFFS%20v4.pdf
Let me know if this helps,
AlexanderHi,
Sorry for the late reply. Somehow the email regarding this post ended up in my spam folder. It seems I have a bug with the “list name detection” in the vLookup script as the proper CAML query parameter should be “Issue%20and%20Process%20Escalation:vLooup” and not “sites:vLookup”.I’ll look into it and post a fix.
PS: When creating vLookup columns, you only have to prefix it with vLookup. Your field names can be like this:
vLookup_issues
vLookup_tasks
and so on…Alexander
Hi,
I have not seed this before, can you post a screenshot of the error message?Could there be some items with item level security, or items with that have lookup columns into other lists that the person does not have access to?
Alexander
