[Alexander Bautz]

Hi,
According to the feedback in this github issue the bug is confirmed and the status is set to “rolling in production”, but I’m not sure when it will be actually rolled out.

Alexander

[Alexander Bautz]

Hi,
Yes, this means these email can only be sent to users registered in the SharePoint site collection. To send to a distribution list using this email method you will have to convert it to a mail enabled security group.

It is not possible to change the “From” address.

To be able to send to external / non-members of the site collection you must set up a FLOW and process the email there.

This is not limitations in DFFS, but in the built-in SharePoint REST API used to process the emails.

Alexander

[Alexander Bautz]

Thanks for the feedback.

I’ll fix the background color on the sticky tabs in the next release, but in the meantime you can fix it by adding this custom css:

.pivotSticky_SUFFIX > div[role='tablist']{
  background-color: #ffffff;
}

I’ll add the “Is empty” and “Is not empty” triggers in the next version.

You can use nested conditions in the main trigger conditions, but I think adding the nesting of conditions inside the “if yes” and “if no” sections will be a bit to complex so you will have to add more rules to handle the different “sub conditions”.

I looked into the “random issue” with the vLookup comfig earlier (I think it was you that mentioned it), but could unfortunately not reproduce it. Did you copy / import the vLookup config or did you create it from scratch?

The grid issue is related to the “row” being rendered using display:flex. It has a default “wrap to new line” if the outer container cannot fit the contents. Can you email me some screenshots so I can look into it and see if it is a bug?

Inline editing in vLookup is unfortunately a bug job to implement so I don’t have time for that at the moment.

Can you give me some more information about adding the class to the fields? – do you mean like adding a classname in the “container styling” property of a field?

Alexander

[Alexander Bautz]

When using the SP.Utilities.Utility.SendEmail endpoint the user must be in the User information list in the SiteCollection for it to work (must be added to a SharePoint group).

I’ll take a look and see if I might be able to run ensureUser on the person in the To-field (to add the user if it is not already in the User Information list) before processing the email in a later version.

Alexander

[Alexander Bautz]

Hi,
I forgot to test it in the WebPart, but will have it fixed hopefully over the weekend.

Alexander

[Alexander Bautz]

Hi,
Is the email address in the “To” field a valid user in the same domain as the SharePoint site where you are sending the email?

Alexander

[Alexander Bautz]

Hi,
I don’t have an example, but found this that basically explains how to set it up: https://sharepoint.stackexchange.com/questions/277676/trigger-email-when-task-due-date-equals-today

Regarding the variables in Custom JS: Those would not be accessible so you would have to write whatever data you want to use in the email to a field in your list item and then pick it up in the FLOW email step. You could create a multiline plain text field and write the email BODY as as HTML string in the field and use that as body in the email.

Alexander

[Alexander Bautz]

There is unfortunately no such feature in the Modern DFFS because emails are sent using the built in REST API.

In the Classic DFFS you had the option to do this by writing the email to a custom list where a SharePoint Designer Workflow triggered and paused the sending until the date was reached.

The way you would do this in SharePoint Online is to set up a Power Automate FLOW directly on that list that runs once a day and sends emails on items where the due date is reached.

Alexander

[Alexander Bautz]

I’ll look into it and see if I can let you override all strings. I’ll try to get a new version out later this week.

Alexander

[Alexander Bautz]

#sbs_FieldTable_YourFieldNameHere is one field (label and body) – and the YourFieldNameHere keyword should be replaced with the FieldInternalName of that field.

If you want to add a border around the entire line (with side-by-side fields) you can use this format (where the number 100 is the side-by-side index used in the tab):

#sbs_OuterTable_100 {
    outline: 2px red dashed;
    outline-offset: 2px;
}

Alexander

[Alexander Bautz]

Hi,
Good idea, I’ll add it to the next version by adding a textarea in the Misc tab where you can add a custom message for each form.

Alexander

[Alexander Bautz]

Sorry, forgot to update you on the new version. I published it on September 15 – Link

If you subscribe to my site or the forum you will get notification when I publish a new version.

Please test and let me know if it fixes the problem.

Best regards,
Alexander

[Alexander Bautz]

I’m not really sure what caused it, but if it has worked fine earlier I assume it must be related to a change by Microsoft.

Alexander

[Alexander Bautz]

@AdamP I have published a new version that hopefully fixes the issue – can you try it out and let me know how it works out?

Alexander

[Alexander Bautz]

Which browser are they using and do you see any errors in the developer tools? (F12 > Console).

Does it work if the user does a “hard refresh” using Ctrl + Shift + r (or clear the cache in the browser settings)?

I’m working on a fix for the issue AdamP reported above, but if you can give me any more details it might help identifying what the error is.

Alexander

[Author]

Posts