InfoPath Dev

I think your post got cut off. Let me know if there is an issue I can help you with.

In the new section, you only want the rows where the SO Number is blank, is that right? I'm sorry - I'm getting confused as to what you want displayed where. At any rate, I made that change in this version. The preceding-sibling rule is so each vendor only shows once? Since I don't know what your list data looks like, I don't know ...

So the original section has two formatting rules on it; the first one is formatting and shows "vendor = preceding sibling::Sharepoint...." (Name: Hide if already displayed) and the other is SO number ≠ SO number (Name: Hide for SO number). I've poked at these rules a bunch, but I cant seem to make it display filtered results based on ...

Another issue occured. I did some kind of VLOOKUP in my from using this default value for my departement field: Title[Name1 = current()/../MANameKompetenz0] (xdXDocument:GetDOM("SMT Orga")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Title[../d:Name1 = current()/../my:MANameKompetenz0]) I connected a second source data to ...

 Hi, I am trying to add additional "Exit" button to your "Form3.xsn" provided in order to be able to exit out the form completely when I type less than 10 characters by using the expression "string-length(.)>10". If I type more than 10 characters and tab out, the comment box will ...

Did you copy the formatting rules from the other table to this one? Right now, there is a formatting rule checking if the SO Numbers match. I think instead you just want to check if the SO Number (in the secondary data source, that the repeating section is bound to) is blank, right? Want to give that a try?

something didn't work, when an SO is selected, if there are no call-ups, the table is still blank. If I select an SO with call-ups, the vendors get displayed properly. I think it has something to do with the rules on the section, not sure what though.

It looks like the first condition on the new table to only show each vendor once might have been causing the issue - I changed that. The vendor name in this case is the "title" field.

Flow is the same thing as Power Automate - Microsoft rebranded it a year or so ago. I'm guessing you'll have a transition phase where you'll be able to get your form published to SharePoint Online, do some testing and add the Flow to populate your list prior to your users starting to use it in the new environment? You'll want to ...

But according to your video it will be possible to use Power Automate to extract the items and add them to a list once we've migrated to SP Online, right? So I would just need a period of time where the old method is "turned off" and then I connect the new Power Automate workflow to the library instead...? I've never used Power ...