[Alexander Bautz]

I’m glad it worked.

Alexander

[Alexander Bautz]

Try it something like the attached code. I have butchered your code a bit so you must edit it to match what you wanted to do after the child list item has been created. See comments in the code and let me know if you have any questions.

Alexander

Attachments:

1. dffs_PreSaveAction_Create_item_in_another_list.txt

[Alexander Bautz]

Hi,
Can you attach the relevant code as a txt-file? – please ensure you strip away any sensitive information.

Alexander

[Alexander Bautz]

I have looked through the old thread you referred to, and from what I can remember (and read) this issue is related to how SharePoint handles the suggestions-menu when it gets so many items that it causes a scrollbar. Somehow this causes the page to jump to the top on older SharePoint versions (it does not from what I can see in SharePoint Online).

Unfortunately I don’t have access to a on-prem SharePoint site anymore so I cannot reproduce this issue.

I think this post related to datepickers might be related so you can try to see if the same approach works (not sure as I’m unable to test it): https://sharepoint.stackexchange.com/questions/227471/sharepoint-date-picker-jumps-to-the-top-of-page-in-chrome-and-now-in-ie

Alexander

[Alexander Bautz]

Hi,
I cannot remember what caused this issue, but try looking at the Misc tab and uncheck the box Scroll to first visible form element in NewForm and EditForm if it is checked. See attached screenshot for details.

Let me know if that doesn’t make any difference.

Alexander

Attachments:

1. 

   Misc_ScrollToFirstVisible.png
   

[Alexander Bautz]

I’m glad you figured out a solution.

Alexander

[Alexander Bautz]

If you can create a view in your list that gives you the items you want, you can get the CAML query using this snippet of code. Just hit F12 to bring up the developer tools, select the Console and paste the below snippet (you might have to type in the text “allow pasting” if you cannot paste the text):

const payload = {
    method: 'GET',
    headers: { "Accept": "application/json; odata=verbose" },
    credentials: 'same-origin'
}

fetch(_spPageContextInfo.webServerRelativeUrl + "/_api/web/lists/getById('"+_spPageContextInfo.pageListId+"')/views/getById('"+_spPageContextInfo.viewId+"')", payload ).then(data => {
    return data.json()
}).then(json => {
    console.log(json);
    console.log(json.d.ViewQuery);
});

Alexander

[Alexander Bautz]

You cannot run async code before save – the built in save method will not wait for it.

I suggest you try triggering the email creation by adding a yes / no field “Schedule emails” or something like that and when you check this field, run your code and then clear all emails in a “Before save of the form” rule.

Alexander

[Alexander Bautz]

Hi,
There might not be your custom code that causes this issue. It could be some kind of validation error after the item has been submitted to SharePoint that causes the item to not save. All emails in the classic DFFS version are sent after the PreSaveAction function (if any) return true, but before the item is actually saved to SharePoint. This means that if there are validation errors on the server side that cancels the save, the email will be sent but no item will be created in the list.

This is a limitation in how the emails work in the classic DFFS version, and if it is causing problems you should use a FLOW (or a SharePoint Designer workflow if you are on-prem) to send an email after the item has actually been saved to the list.

Alexander

[Alexander Bautz]

Look at the change log for v1.0.75.0 and see if you can use the variables I exposed to accomplish what you want to do.

PS: I just published v1.0.76.0 also: https://spjsworks.com/changelog/

Alexander

[Alexander Bautz]

Sorry, but I don’t think this kind of solution can be added to DFFS. This is because it in any case requires an external list and a custom FLOW to send the emails, and the technical setup of this would cause a lot of support requests…

I think you are better off setting up a FLOW that runs on a schedule (every hour or every day) looking for items in the list that matches the send date set in a datepicker in the list item. Using a FLOW you can set up different conditions for different statuses, and send emails based on different schedules that reads the data from the list item directly when you send the email in the FLOW.

Alexander

[Alexander Bautz]

I have added a new option “Clear the previous value before setting new value” to the Set field value action in the rule-builder.

Alexander

[Alexander Bautz]

You can use the DFFSID (you must add a field with internalname _DFFSID your list and the DFFSID will be autogenerated) like this from an email triggering on any trigger you like:

Here is the new item: <a href="https://contoso.sharepoint.com/sites/YourSite/Lists/YourList?DFFSForm=disp&DFFSID=[[fieldValue:_DFFSID]]">Link</a>

Scheduling emails is not possible directly from DFFSS. You must use a FLOW to achieve this (by adding a send-date field in your list item and using a FLOW that runs on a schedule every day looking from send-date match in the list).

Alexander

• This reply was modified 2 months ago by Alexander Bautz. Reason: Fixed link-format

[Alexander Bautz]

Hi,
Are both of your people picker fields multichoice?

Alexander

[Alexander Bautz]

Hi,
This issue is fixed and I’ll release a new version tomorrow.

Alexander

[Author]

Posts