-
Search Results
-
Topic: Unlicensed user issue
I am encountering an issue I am struggling to properly address, and I was wondering if you might be able to resolve it in code or have any suggestions. We have modern DFFS handling forms on some lists which have people fields. When a user leaves our company, their account is disabled, and their license is removed. I am finding when a form is edited which includes one of these disabled and unlicensed users, the form cannot be saved because of an error in the “validateupdatelistitem” call that occurs prior to the form being saved. The error is, “We couldn’t find an exact match.”
I have also noticed that when one of these users exist in a list item, they do appear in the display form, but when I go to edit the form, the user does not appear in the people field because they did not resolve properly in the people picker. However, unless I modify the people field, the unresolved user will be sent to the “validateupdatelistitem” endpoint—even though they are not visible in the edited form—and cause the error explained above.
I can see the network calls to “_api/SP.UI.ApplicationPages.ClientPeoplePickerWebServiceInterface.clientPeoplePickerSearchUser” where the unlicensed users return empty values and the licensed users return all the data the people picker needs. Is it possible for you to handle removing users who do not resolve when the edit form loads the people fields so they are not passed to “validateupdatelistitem” prior to saving?
I upgraded from 1.0.64.0 to 1.0.70.0
When I look at
Site Contents > Modern DFFS > Details
It correctly shows
VERSION 1.0.70.0However, when I click on the DFFS link on a list, the first screen shows
“Dynamic forms for SharePoint”
v1.0.64.0Any suggestions?
Thanks
/MarcusHey Alexander! First off, I’m devastated lol. I had a huge list of bugs and enhancements in a file for you and I don’t know what happened but the company pushed an update to my machine and it wiped the location that file was stored. I haven’t been able to recover it. So, the below list is only a partial list of the bugs and enhancement requests I have identified so far within modern DFFS. I understand some of this stuff is probably complex and will take time or just not a priority, so no worries. Just want to put it out there 🙂
— When tab bar is locked you can see the form behind it and the little gray bottom border bar overlaps that content. I think the enter tab row should have a solid white background to look better.
— Can “is empty” and “is not empty” be added to the rule conditions, especially for date and people fields?
— Can the “yes” or “no” sections have nested conditions? For example, say I have a rule that says if x is equal to y. Let’s just say that results to true. Now, let’s say I have a scenario where I want to check another condition in both the true and false sections, because that will determine what I do next. Can we have a condition nested here, or what do you recommend? Of course, I could just create additional rules that key off the parent, but it’d be cool if they could nest. Let me know if you need more clarification on this. It might be too complex.
— Having a random issue that I cannot track down with vLookup. I’ll build the table, then build the add new form with prefills. If i edit the table, sometimes it totally messes up the add new form prefills. It’ll like remove fields I set, I don’t get it. It seems to happen if I remove fields in the “build the table” section and save and go back in and now the prefill fields tab has totally different fields than what I originally had in there.
— Having an issue with grid form where say I set a form row with multiple columns. Let’s say 3 columns. Column 1 I go with 6, column 2 will be set to 4 and column 3 I set to 2. If I put a field in column 3 that is somewhat wide, then in the form editor those 3 columns aren’t appearing side by side like they should. They do when I preview the form, it looks fine there, but in the column editor for some reason it’s wrapping, and I’ll find column 3 below columns 1 and 2. It’s not a big deal, it’s just cosmetic.
— Is inline editing possible to be added to a vlookup table?
—Can you have it to where we can add a class similar to how you have JS customizer function name references. This would be both for normal fields and for vLookup. That way I can add CSS to the class, easier than doing CSS via JS.
Hi Alex,
I am encountering an error while trying to send an email from DFFS. Error pop up shows message “The e-mail cannot be sent. Make sure the e-mail has a valid recipient. Here is the setup.
Form: Edit form
Trigger: before save
Actions: Prepare an email
Email has all the required fields. Its a simple test list. When an item is saved
– I see the following in network tab
Request URL: https://xxxx.sharepoint.com/sites/xxxx/_api/SP.Utilities.Utility.SendEmail
Request Method: POST
Status Code: 400 Bad Request
Payload: {“properties”:{“To”:[“webadmin@ltp.org”],”Subject”:”Test email”,”Body”:”test email”}}Response is
{
“odata.error”: {
“code”: “-2130242040, Microsoft.SharePoint.SPException”,
“message”: {
“lang”: “en-US”,
“value”: “The e-mail message cannot be sent. Make sure the e-mail has a valid recipient.”
}
}
}Please advise
Hi Alexander
I’ve just seen your update about v1.0.67.0 which I’ll upgrade to ASAP, but currently we’re on v1.0.66.0 and experiencing issues with Modern DFFS not loading for a significant proportion of users (identical permissions and desktop setup), likely since the Microsoft changes around 4th September.
I can’t see anything yet that gives a clue as to the difference between those it works for and those it doesn’t, but the users in each camp are consistent.
The list view is embedded into a SharePoint page, and I’m still trying to determine if it’s the same behaviour when accessing the list directly (difficult because it works as expected everywhere for me).
For users where Modern DFFS fails, the item link is clicked on, and instead of the (DFFS) dialog box popping out, a new tab opens with the non-DFFS item url in, showing the default SharePoint form (see attached for url format).
In the console there is a DFFS-command-set error that appears at the point the list item title is clicked (see attached).Any ideas on what might be the cause and any possible fixes? Looking at the page source it looks like the listBaseTemplate might be 119 – wiki page library, and 100 for the list customised with Modern DFFS. The strange part is that it works normally for some users and not at all for others.
Thanks
Adam