Forum Replies Created
-
AuthorPosts
-
I did one change in v1.0.67.0, but I’ll look into it again and se if I can get a fix into the next upcoming release. I plan to release it over the weekend.
Alexander
Hi,
Which version of Modern DFFS are you running?Alexander
I thought all issues were resolved, but when I do a test now it seems the DFFS banner button only shows when you reload the page and not when you navigate using the left side menu (quick launch) between lists.
In my case, the command-set extension is still active and working, but the DFFS banner button is not showing unless you reload the page.
I’ll investigate, but in the meantime can you check if there are any errors in the developer console (F12 > Console) when you load the page, and if the banner button shows if you reload the page?
You can email me any screenshots if you like.
Alexander
Thanks for your donation.
You can set the width for example in percent using the “Style” textarea of the field setup in the vLookup config. For example like this:
width:20%
I’m not able to recreate the decimal issue on number fields. Have you specified the number of decimals in the list settings in the list you are pulling the values from?
Regarding the styling: There are unlimited possibilities so it’s hard for me to think of what could be useful. Can you give me some examples of what you think of here? – no-wrap on the field label, or when you use side-by-side with multiple fields?
Best regards,
AlexanderI’m guessing this must be a caching issue in your browser. Try clearing the cache either in the developer tools or in the browser settings.
Alexander
Sorry, I thought I had replied, but cannot find my reply anywhere.
I’m not able to recreate the issue with setting a PP and using it in an email as recipient – if you can email me or post some screenshots so I can see exactly how you have it set up I can try to replicate it.
I have added new triggers that will fix the second question by adding a trigger “is changed from initial value” – combine two triggers like this:
AND
— Field is equal to Yes
— Field is changed from initial valueI’ll try to get it published later this weekend or early next week.
Alexander
Add a new email using the button shown in the attached image.
Regarding the other issue: I cannot find my reply – something must have failed when I posted it. I’ll reply again in the other topic.
Alexander
Attachments:
Hi,
Sending multiple emails can be done – just click “Add” below the first one to add another.I’ll add similar functionality to the “Call a function” step.
As mentioned earlier I’m not able to recreate the issue you reported earlier regarding setting a people picker and using that people picker in an email – could you email me some more information (screenshots) so I can replicate the exact same setup as you have?
Alexander
It seems like Microsoft has again rolled out a new update to the List View UI that breaks Command Set Extension solutions (like the Modern DFFS). I have filed two bug reports with Microsoft related to the latest rollout and hope they respond quickly to fix the issues.
You can track any updated from Microsoft on the issues here:
https://github.com/SharePoint/sp-dev-docs/issues/9953
https://github.com/SharePoint/sp-dev-docs/issues/9954Sorry for the inconvenience.
Best regards,
AlexanderCan you email me some screenshots of the page with F12 > Console open when you load the page?
Alexander
Hi,
You can do this by creating a rule that triggers on “Form is loaded” and in the “if yes” select the “Call a function”. Add the name of the function like this:hideEmptyFields
Now add this to your Custom JS and change the “arr” to include the FieldInternalName of the fields you want to check for empty.
function hideEmptyFields() { var arr = ["Field1", "Field2", "Field3", "Field4"]; arr.forEach(fin => { if (String(getFieldValue(fin)) === "") { document.querySelectorAll("div[data-fin='" + fin + "']").forEach(row => { row.style.display = "none"; }); } }); }
Alexander
- This reply was modified 2 months, 2 weeks ago by Alexander Bautz. Reason: Fixed wrong trigger name
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
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
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
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
-
AuthorPosts