Search Results for 'list form'

[Alexander Bautz]

Are you 100% sure you have the same version loaded in your “frontend”? – check the Enhanced with DFFS link below the form to see the version loaded.

Also, are you sending any emails in this form when it is saved? – the original dual-call-dffs_PreSaveActoin-bug was related to the email processing.

If it is the correct version I need to see your custom js. If you don’t have any sensitive info in it you can post it here – alternatively you can email it to me (on the address you get this notification from).

Using this code in NewForm will always show the message as it does not check to see if the field are filled. It is possible to do that and only show the message if you are missing input in some fields, but you should turn on the “Show list of empty required fields when attempting to save the form” feature in the Misc tab instead.

Alexander

[Ross]

Hi Alexander,

Would you be able to take a look at a potential bug when the Require Checkout feature is enabled.

Issue

When a user edits and item that is not currently checked out they are unable to cancel the form and close the dialog.

The window checkin/out prompts loop without closing the dialog.

Replicating

1. Navigate to /sites/dffs/Lists/CheckInOutBug/AllItems.aspx
2. Ensure the item is currently not checked out.
3. Edit the item
4. Click “OK” to checkout the item.
5. Click “Cancel”
6. Click “OK”
7. “Repeat steps 4-5” and the form can never be cancelled.

Environment

SharePoint 2010
Browser (Chrome, Edge, IE Doc Mode 10)

Version information

DFFS Loader: v1
DFFS frontend: 4.4.5.25 – May 17, 2021
DFFS frontend CSS: 4.64
Autocomplete: – April 25, 2021
Cascading dropdowns: 3.7.46 – March 21, 2021
jQuery: 1.12.4
Lookup: 1.1.20 – March 10, 2020
Resource management: not loaded
SPJS-Utility: 1.350 – February 21, 2021
vLookup: 2.2.161 – March 21, 2021

If you open an item that is already checked out. Clicking save correctly closes the dialog.

• This topic was modified 4 years ago by Ross.
• This topic was modified 4 years ago by Ross.
• This topic was modified 4 years ago by Ross.

Attachments:

1. 

   Checkout-Loop.png
   

[Alexander Bautz]

You must add the line to the custom js as I described earlier – this hides the parts outside the form.

The redirect page is necessary because the form lives in an iframe (a window) in the page – when submitting the form, this window will either show your “receipt page”, or it will redirect to the default list view of the list you have added an item to – still in the window in your modern page.

Alexander

[Alexander Bautz]

You should be able to use the “Embed” webpart in a modern site – use an iframe like this:

<iframe width=800 height=1000 src="https://contoso.sharepoint.com/sites/Engineering2/Lists/list2/NewForm.aspx?Source=/sites/Engineering2/SitePages/Success.aspx">

Alexander

[Alexander Bautz]

Hi,
DFFS is only designed for the default forms so adding it in an iframe might not work properly. I did test with a page viewer web part and added the link like this:

https://contoso.sharepoint.com/sites/Engineering2/Lists/list2/NewForm.aspx?Source=/sites/Engineering2/SitePages/Success.aspx

The Source URL parameter points to a page you need to create that has a “Thank you for submitting the form” message.

In your NewForm Custom JS you must add this line to hide all but the form (so you don’t get the left menu and all the SharePoint UI rendered in the iframe:

jQuery("body").addClass("ms-fullscreenmode");

Let me know how it works out.

Alexander

[William Ellis]

I am attempting a similar solution, except that I am not using Boolean, I am checking Choice fields, so I made some changes. Each Initiative has several Assignments as children. If any children have Status != ‘Completed’, then I want the alert to show and not allow them to save the Initiative Status on the parent record as ‘Completed’. I have placed this in my parent Edit form CustomJS tab, but nothing happens when I save and have the Initiative Status set to ‘Completed’. I’m sure thee is something wrong with my script but I cannot see what that might be.

function dffs_PreSaveAction(){
// Check if parent form is closing
var initStatus = getFieldValue(“InitiativeStatus”); // Get Initiative Status value
if(initStatus=”Completed”){
var res = spjs.utility.queryItems({
“listName”:”Assignments”,
“query”:”<Where><Eq><FieldRef Name=’_vLookupParentID’ /><Value Type=’Text’>[currentItem:_vLookupID]</Value></Eq></Where>”, // Lookup parent ID
“viewFields”: [“ID”,”Status”] // return ID and Status of assignment records
});

if(res.count > 0){
var allStatus = true;
jQuery.each(res.items, function(i, item){
if(item.Status != “Completed”){
allStatus = false;
}
});
if(!allStatus){
spjs.dffs.alert({
“title”: “Not able to close”,
“msg”: “You cannot set the Initiative Status to Completed until all Assignments are Complete.”
});
}else{
// OK to save
return true;
}
}else{
// Does not have any child items – return true to save item
return true;
}
}else{
// OK to save
return true;
}

[Harsh]

I created DFFS form for one list and i want to add this list into homepage of SharePoint Online site.
I used Embed webpart and add DFFS forms link with iframe tag as per below.

“https://contoso.sharepoint.com/sites/Engineering2/Lists/list2/NewForm.aspx”

but it not work for me….can anyone help me to get only weblink of DFFS form just like we can get link of powerapps form?

Thanks in Advance.

• This topic was modified 4 years ago by Harsh.
• This topic was modified 4 years ago by Harsh.
• This topic was modified 4 years ago by Harsh.

[Ross]

Hi Alex,

Overview

Rules with User fields with on change triggers cause unexpected results that make multiple calls to functions/alerts etc.

In Internet Explorer and Edge (Chromium v88) the screen also flickers briefly which is very distracting for users but not a breaking bug.

Environment

• SharePoint 2010
• Document Mode 10 (for IE only)
• Internet Explorer 11 (in 10 mode)
• Edge Chromium v88
• Chrome v90 (no screen flickering issues)
• DFFS Release Date (Production Version): DFFS_2021-05-10

Replicating the Issue

1. Create a list with a user field
2. Create rule that triggers on user field change and displays an alert of “Rule Called”
3. Open the form and enter a valid user. The alert should be displayed
4. Clear the user by using the delete/backspace key
5. The alert will be displayed.
6. Wait for a few seconds and the alert will be displayed again

I have had issues replicating the screen flickering issue but can provide a video soon (new computer and no video capture software installed today).

Testing

I have replicated the issue on our development environment which you have access to via the VPN.

The URL ends with …tpoint/sites/dffs but I can email you the address if you don’t have it handy (don’t want to write it in here).

If you do want to check it out I have added instructions on the home page of the site.

If there is anything else I can provide that will help, please let me know.

• This topic was modified 4 years ago by Ross.
• This topic was modified 4 years ago by Ross.

Attachments:

1. 

   User-Field-Rule-Bug.png
   

[Alexander Bautz]

Hi,
Have one of the affected users hit F12 to bring up the developer tools and select the Console tab to look for any error messages there when hitting the save button.

If you don’t see any errors there it might be a hidden field that has a validation error – either a people picker that is auto-filled, but not properly validated or maybe a date field with an invalid date value.

As part of the troubleshooting you can add a new tab to the form where you don’t add any fields – this tab will now show ALL fields available in the list, and you can look at this tab to see if it is a validation error on one of the fields that prevent saving.

If this doesn’t help you might have an error in your custom js – keep in mind that returning false in a function named “dffs_PreSaveAction” will prevent saving the form (no notification, just nothing happening).

Let me know how this works out.

Alexander

[Keith Hudson]

Here are some things to check: 1. You mention that select users who are in the “Secondary Review Team Members” permission group are able to click the Save button with no issues. Does that permission group have Contribute access on the list? Or are the ‘select users’ given Contribute some other way? If the group itself is not given Contribute on the list, try giving the group itself Contribute permissions.
2. Although you say that the impacted users ‘cannot click the Save button’, you don’t say whether the button is missing from the form for them, or whether they get some kind of error message (or no response at all) when they try to click the button. Check the advanced settings on the list to be sure that the list is NOT set to only allow users to edit items they have created. OR, if that setting IS set, and is needed, give the “Secondary Review Team Members” permission group Design permissions on the list.

These two things may not work, but they are worth checking.

Alex may have additional suggestions.

[Alexander Bautz]

Hi,
A date field without the time part visible will always set the time to 00:00:00. SharePoint stores the dates as UTC in the DB and will automatically correct for the timezone / daylight saving time when saving the value. This means the value is off by in your case two hours – and this sets the date to the previous day.

The normal list views in SharePoint corrects this back when rendering the value, but this plugin does not do that automatically.

You can try to fix this by using a calculated column in the list you are looking up in and set the formula like this:

=TEXT(Created,"yyyy/MM/dd")

Replace Created with your field name.

Now use this field in your cascading dropdown config and not the original date field.

Let me know how this works out.

The error you get when updating is most likely caused by one of the fields being empty – can you confirm this so I can look into this bug and fix it?

Alexander

[Steve]

Hi Alex,
I’ve started working on cascading dropdown in the morning and everything was fine. But suddenly, cascading dropdown begun to offset date minus one day.
1. Attachment – source list with data about products and expiration date.
2. Form in the current list item to show the date for the product.

See more in the attachment.
Thank you for your reply.
Steo

• This topic was modified 4 years ago by Steve.

Attachments:

1. 

   DFFS_date_field_casc_dropdown.png
   

2. 

   DFFS_version.png
   

[Keith Hudson]

I have noticed that recent versions of DFFS (eg. 4.4.5.17) no longer send me back to the form I was configuring when I exit the configuration, but rather send me back to the default view of the list with which the form is associated.

This really slows down my development efforts. Is there a way to change this behavior? Or some reason the change was made? Is it a bug you haven’t been aware of, Alex?

If the change is deliberate and permanent, can you tell me what version first made the change? I haven’t seen a note of the change in the Change Log. I’ve searched on the Change Log page for the following strings, with no results showing: ‘Default View’, ‘Exit Configuration’, ‘Configuration Behavior’.

In case it matters, I always use the v1 DFFS Installer, never v2.

[Alexander Bautz]

Hi,
I would recommend setting the field as NOT required in the list settings and then use a DFFS rule to set it as required. This would ensure it always default to “(None)” on load and you can use this snippet:

function dffs_PreSaveAction() {
    if (String(spjs.dffs.beforeProperties.LookupProject) === String(getFieldValue("LookupProject"))) {
        spjs.dffs.alert({
            "title": "",
            "msg": "Please select a value in the field <strong>" + spjs.dffs.fieldData.LookupProject.disp + "</strong> before trying to save this item."
        });
        return false;
    }
    return true;
}

If you cannot remove the required setting from the list settings you must use something like this, but please note that if your form encounters a validation error after postback to the server (for example a date filed being on the wrong format, or if you have some kind of validation set using Column validation in the list settings) this will see the now selected value as the “load-value” and require that you change it before saving:

var lookupFieldLoadValue = getFieldValue("LookupProject");
function dffs_PreSaveAction() {
    if (lookupFieldLoadValue === getFieldValue("LookupProject")) {
        spjs.dffs.alert({
            "title": "",
            "msg": "Please select a value in the field <strong>" + spjs.dffs.fieldData.LookupProject.disp + "</strong> before trying to save this item."
        });
        return false;
    }
    return true;
}

Please replace “LookupProject” with the internal name of your lookup field.

Alexander

[MikeS]

I need to perform error trapping on a New form before it is saved and a SPD workflow kicks off.

The script should check that one or more single lookup fields have been changed from the default that loads with the New form. A lookup field could be:

1) blank when the New form loads – displays “(None)” or

2) (if the lookup field is required) it would default to the first entry of the list to which the lookup is being performed on.

The validation would check to see if these lookup fields had been changed from the default, and if not, require the user to fix the error before the form can be saved.

Thanks for your help,
MikeS