cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

ForAll working inconsistently - why?

Hi,

 

I have 3 tables:  "Job Setup" (a header record), "Project Job Category" (a line item to Job Setup), and "Job Category" (a set of default records I want to use to create the line items).  Every time I create a header, I want to copy over the records from "Job Category" to "Project Job Category" as a starting point for the user to further edit.  "Project Job Category" has lookups to both of the other tables mentioned.  In other words, "Project Job Category" is a join table, representing a many-to-many relationship between "Job Setup" and "Job Category".

 

I can iterate "Job Category" successfully with a ForAll, using Collect to visualize that I am indeed looping multiple times.  However, when I try to ForAll through "Job Category" to create the "Project Job Category" rows, it only runs once.  There are about 10 "Job Category" records.

 

For example, I successfully iterate over Job Category here:

 

//This iterates multiple times and successfully creates multiple records in the collection (as intended)
ForAll(
    ['Job Categories'],
    Collect(
        TGTestCategoryIdCollectionFromForAll,
        'Job Categories'
    )
);

 

 

But when piecing this together with a patch, it only runs once:

 

//This creates a single linked record successfully, but only iterates once... why?
ForAll(
    ['Job Categories'],
    Patch(
        'Project Job Categories',
        Defaults('Project Job Categories'),
        {
            'Job Category': LookUp(    //Use lookup because I can't figure out how to reference the current record from ForAll
                'Job Categories',
                'Category ID' = 'Job Categories'[@'Category ID']
            ),
            'Job Setup': gblSelectedJob   //gblSelectedJob is the Job Setup that I want to link to
        }
    )
);

 

 

Questions:

-Why does the second ForAll only run once when the first one runs multiple times?

-Is there a better way to create some default records in one step than this?

 

Thanks for any help or guidance, much appreciated!

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Hardit,

 

Eventually found the solution.  Here is the working version in case it ever helps.

 

The required changes were:

  1. Changing syntax of table references... note the lack of braces in ForAll, but the inclusion of [@..] braces in table references inside the Patch
  2. Adding of RenameColumns in ForAll, to eliminate ambiguity the in LookUp
  3. Had to reference some of the columns by their internal name in order for the formula editor to accept them. Not sure why.

Final version

//This works
ForAll(
    RenameColumns('Job Categories', "cr8b0_jobcategoriesid", "Category ID Tmp"),
    Patch(
        [@'Project Job Categories'],
        Defaults([@'Project Job Categories']),
        {
            'Job Category': LookUp('Job Categories', 'cr8b0_jobcategoriesid' = 'Category ID Tmp'),
            'Job Setup': gblSelectedJob
        }
    )
);

 

Thanks for the help thinking through it, much appreciated!

View solution in original post

10 REPLIES 10
PowerAddict
Most Valuable Professional
Most Valuable Professional

Have you tried?

//This creates a single linked record successfully, but only iterates once... why?
ForAll(
    ['Job Categories'],
    Patch(
        'Project Job Categories',
        Defaults('Project Job Categories'),
        {
            'Job Category': the field in Job Categories which is a lookup to Job Category,         
            'Job Setup': gblSelectedJob  //gblSelectedJob is the Job Setup that I want to link to
        }
    )
);

 

Let me know if this helps. If not, I will share an example that might give you an idea. 

 

---
If you like this reply, please give kudos (Thumbs Up). And if this solves your problem, please mark this reply as a solution by selecting Accept as Solution. This makes it easier for others to find answers to similar questions. 

 

Thanks!

Hardit Bhatia

Blog | Twitter | LinkedIn | Facebook | YouTube  |  Email

Anonymous
Not applicable

Hi Hardit,


Thanks for the reply.

 

It doesn't like that, it is seems to want the entire record for that reference....

 

 

Annotation 2020-04-09 114857.png

Can you show me the data structure? Sorry if you have answered this before, but are these SP lists or collections or some other data source? 

 

What is the lookup field on the Job Categories table that references the Job Category? The one referenced below in your screenshot is the Job Categories table which is why you are getting the error that it needs a record, not a table. 

 

Let me know. 

 

---
If you like this reply, please give kudos (Thumbs Up). And if this solves your problem, please mark this reply as a solution by selecting Accept as Solution. This makes it easier for others to find answers to similar questions. 

 

Thanks!

Hardit Bhatia

Blog | Twitter | LinkedIn | Facebook | YouTube  |  Email

Anonymous
Not applicable

Hardit,

 

These are CDS entities.

 

Here is the schema for Project Job Category (records I am trying to create), and Job Category (records I am trying to loop through).

 

Job Category is a simple list entity, just the ID GUID column and a name column for the name of the category.

 

Project Job Category is the join table - with a lookup each to Job Setup and Job Category (Job Setup and Job Category, respectively).  The Job Setup relation is working fine, so not including that schema.

 

 

 

Job Category Schema.pngProject Job Category Schema.png

Try this: 

ForAll(
    ['Job Categories'],
    Patch(
        'Project Job Categories',
        Defaults('Project Job Categories'),
        {
            'Job Category': LookUp('Job Categories', 'Category ID' = 'Category ID',         
            'Job Setup': gblSelectedJob  //gblSelectedJob is the Job Setup that I want to link to
        }
    )
);

What I am trying to do here, is inside my Patch, for the Job Category lookup field, I am using a lookup to Job Categories, using the ID of the category ID of the current row in the ForAll loop. The reason I am using LookUp is because there is no way to fetch the entire record within a ForAll loop. 

 

Let me know if this works. If not, I will replicate your use case using real entities and give you an answer. 

 

---
If you like this reply, please give kudos (Thumbs Up). And if this solves your problem, please mark this reply as a solution by selecting Accept as Solution. This makes it easier for others to find answers to similar questions. 

 

Thanks!

Hardit Bhatia

Blog | Twitter | LinkedIn | Facebook | YouTube  |  Email

Anonymous
Not applicable

Hardit,

 

That version is accepted by formula editor.  When it runs though, it doesn't successfully find the Job Category and set it.  You can see the result in the first row shown below.

 

Adjusting it slightly gets us back to the formula I had in my original question.  The record also gets created, but the Job Category is set correctly.


In either version - the ForAll only loops once, or at least only creates 1 Project Job Category record (the screenshot shows the process having run twice - first row with your formula, the second with ('Category ID' = 'Job Categories'[@'Category ID']) instead of ('Category ID' = 'Category ID').

 

I also included screenshot of rows in Job Category for reference - there are 12, so I expect 12 Project Job Category records to be created.

 

What is created from two different function versions:

createdRecordsExample.png

 

Data in the Job Category table:

jobCategoryRows.png

In trying to replicate your scenario, do you think I would need Job Setup or can I ignore that lookup field in Project Job Category? 

 

---
If you like this reply, please give kudos (Thumbs Up). And if this solves your problem, please mark this reply as a solution by selecting Accept as Solution. This makes it easier for others to find answers to similar questions. 

 

Thanks!

Hardit Bhatia

Blog | Twitter | LinkedIn | Facebook | YouTube  |  Email

Anonymous
Not applicable

I think you can ignore it, that part is working OK.

Anonymous
Not applicable

Hardit,

 

Eventually found the solution.  Here is the working version in case it ever helps.

 

The required changes were:

  1. Changing syntax of table references... note the lack of braces in ForAll, but the inclusion of [@..] braces in table references inside the Patch
  2. Adding of RenameColumns in ForAll, to eliminate ambiguity the in LookUp
  3. Had to reference some of the columns by their internal name in order for the formula editor to accept them. Not sure why.

Final version

//This works
ForAll(
    RenameColumns('Job Categories', "cr8b0_jobcategoriesid", "Category ID Tmp"),
    Patch(
        [@'Project Job Categories'],
        Defaults([@'Project Job Categories']),
        {
            'Job Category': LookUp('Job Categories', 'cr8b0_jobcategoriesid' = 'Category ID Tmp'),
            'Job Setup': gblSelectedJob
        }
    )
);

 

Thanks for the help thinking through it, much appreciated!

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (3,957)