[Jorah Lavin]

Thanks, Alexander. I’ll share this news with my team.

[Jorah Lavin]

Alexander, you truly are the Keymaster! That’s going to make my work a lot easier.

Thank you from me and on behalf of the folks who will be working on this inventory.

[Jorah Lavin]

Thanks for that, EJ! I have ShareGate, and will reach out to coworkers with experience with PowerShell to see if they can assist.

[Jorah Lavin]

Thanks, I’m now bewildered that I haven’t seen the ‘Suggested Items’ feature previously. I’ll go back and look at my previous form (unless the difference is because most of these I’ve done have been cascading menus…?)

[Jorah Lavin]

Thanks, Alexander. I got the user to share screen, and when they’re viewing any SP list with DFFS enabled, when they look in the Console, we can see the blocked query as you describe, but it’s not affecting me or others using DFFS. If the resource was blocked at the enterprise level, I’d expect that DFFS just wouldn’t work. Why would it be blocked for some users?

[Jorah Lavin]

Alexander, please disregard my question from July 6 about multi-select. I figured it out after building a trio of test lists. I had the wrong internal name on my filter…

[Jorah Lavin]

Hi, Alexander.

As a follow-up on the cascading menu question, after getting the cascade working, the client has come back to say that the subsidiary menu must be multi-select. For instance, to follow the example you used in your user manual, they are asking that when the user selects a Country, they should then be able to select anywhere from 1 to 5 Regions from the cascaded menu.

So…

Drop-down one: Choose ‘US’
Drop-down two: Choose ‘Massachusetts’ and ‘Vermont’

I’ve read through the manual and looked at settings in DFFS and can’t find a way to work this. I thought I might change to using the ‘lookup field’ instructions in the DFFS User Manual, but I haven’t been able to get the subsidiary menu to be controlled by the main menu.

[Jorah Lavin]

Marcus, on our team we’ve been supplying DFFS links, which avoid the ‘wait for DFFS to load’ issue… It works for many use cases, but not all.

[Jorah Lavin]

I’m the cause of the confusion, Keymaster! It’s because our company has to review and sign off on every version we use, so we’re almost always 4-6 weeks behind. We got special dispensation to jump from .22 to .26, but I am not expecting a new upgrade until mid-July now.

[Jorah Lavin]

Thanks, Alexander! I’ll be watching for an update to our ‘official’ reviewed version to overcome that empty form bug. Your remark about the DFFSID/form parameters is helpful, I’ll watch for that.

-Jorah

[Jorah Lavin]

Thank you, sir! I’m going to dive into Power Automate to see if I can figure this out.

[Jorah Lavin]

Thanks, Alexander. I appreciate you and this amazing toolset you’ve built. Everyone I show the new DFFS to is astonished by it!

[Jorah Lavin]

I finally found the name of the connector we’re not allowed to use, it’s ‘SendGrid Mail connector v2’ and ‘SendGrid Mail connector v3’

[Jorah Lavin]

Thank you, Alexander! I was able to get this running, and it’s very nice. This is what I ended up with in my Set Field Value:

=============================================
Edited on [[timestamp:{“date”:”today”,”offsetDays”:0,”format”:”MM/dd/yy at HH:mm”}]] by [[currentuser:displayName]]
Comment: [[fieldValue:Comment]]
-=-
[[fieldValue:History]]
=============================================
After seeing how this worked in DFFS I was able to replicate it in Power Automate as well, which will be handy for folks in the company who don’t have access to DFFS.

Attachments:

1. 

   2023-05-01_08-03-34.png
   

[Jorah Lavin]

Interesting thought about the special characters in the list name; there was a slash in the name, although not in the original list creation name, so I’ve replaced that with a dash and we’ll see if the problem rears its ugly head again. Thanks!

[Author]

Posts