Trying to Create An Acknowledgement Flow and Receiving this Error

Options

Comments

  • Glen Hutson
    Glen Hutson Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    Hi Jessica,

    The “Simple Receipts” document, how was that created? Did that start with one of our samples or from a pre-existing document with merge fields? The templates for Power Automate use newer Content Controls rather than the older Merge Fields. The error that's popping up typically indicates that the file you're pointing to doesn't have any Content Controls. You can take a look at the following tutorial for example templates as well as how to update both the templates and your flow with additional fields.

  • Hi again,

    Now I am trying to customize the template per the referenced article but getting the following error message. Any ideas? Thanks!

    7717193a87e7c040f8ee3297a75d5f58-huge-fl
  • Glen Hutson
    Glen Hutson Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    Hi Jessica,

    The picture didn't come through too clearly on this end, but it appears that you're trying to also include the Fund Description? If so, check out the below post and associated video that walks though a general discussion on working with the likes of Fund Description and Payment Methods in Power Automate + Raiser's Edge NXT scenarios. The way that those and other fields work in Raiser's Edge NXT, it tries throwing in yet another loop which the process doesn't like.

  • c041b9d738dfa1fbd8ad1977c65c2184-huge-fl

    Thanks, Glen. The error is actually happening with any field I try to add in, though your link is helpful. It says the flow saved failed with code “InvalidTemplate” and template validation failed because of nested actions.

  • Glen Hutson
    Glen Hutson Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    Jessica Clark:

    c041b9d738dfa1fbd8ad1977c65c2184-huge-fl

    Thanks, Glen. The error is actually happening with any field I try to add in, though your link is helpful. It says the flow saved failed with code “InvalidTemplate” and template validation failed because of nested actions.

    Hi Jessica, the “template validation failed because of nested actions” is probably due to the fact something got added (Gift Splits Fund ID for example) that threw the whole area into a second “Apply to each”… that's why you see the “Apply to each 2” at the top of that screenshot. There shouldn't be an “Apply to each 2” there. Once the Apply to each 2 shows up, even removing the field that prompted it won't remove the Apply to each 2 automatically. The video link gives some hint into how you can remove the “offending” field, take the whole block out of the Apply to each 2 and then remove the Apply to each 2. At that point, if you want to add the Fund Description, that's where the steps indicated in the video come into play: Using the “first” function to isolate the first Gift Splits Fund ID and then using that to “Get Fund” before adding a field to the overall Append area.

  • Got it! That was really helpful.

  • @Glen Hutson
    In one of your tutorials you mentioned you use a mac but have to toggle over to windows for certain things. Is there a mac equivalent for plain text content controls in word for macs that has worked for you? Or do you create and update word docs in windows?

  • Glen Hutson
    Glen Hutson Blackbaud Employee
    Tenth Anniversary Kudos 3 Name Dropper Participant

    @Beth Dow:

    @Glen Hutson
    In one of your tutorials you mentioned you use a mac but have to toggle over to windows for certain things. Is there a mac equivalent for plain text content controls in word for macs that has worked for you? Or do you create and update word docs in windows?

    On a Mac, you can take the current fields and move them around, that's about it. The part of the Development tab in Word that deals with the actual creation of those controls hasn't made it over to Mac yet and I haven't found an alternative. I'm having to hop over to a Windows machine to do those.

  • @Glen Hutson ok thanks. That's what I thought, but was hoping I was just missing something.

Categories