cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
akg1421
Advocate II
Advocate II

Error when Filtering data source before Creating a Collection

Using mydatasource to create mycollection1 before filtering mydatasource to return only specific rows

ClearCollect(mycollection1,Blank());
ForAll(mydatasource As mydatasource,
	Filter(mydatasource,mydatasource.UserId="Jonathan"),
    Collect(mycollection1,
        {
            FullNameOriginator: LookUp(mycollection2, ID = mydatasource.'User (Originator)','Person name'),
            Status:mydatasource.Status,
            'User (Originator)':mydatasource.'User (Originator)',
            Subject:mydatasource.Subject,
            'Work item instructions':mydatasource.'Work item instructions',
            WorkflowWorkItemClaimed:mydatasource.WorkflowWorkItemClaimed,
            'User (UserId)':mydatasource.'User (UserId)',
            'Due date time':mydatasource.'Due date time'
        }
    )
);

I want to create collection based only on filtered rows returned from my datasource. In above query I am trying to filter but it returns error.

 

Is the syntax correct?

1 ACCEPTED SOLUTION

Accepted Solutions

@akg1421 

 

The second one is closer, but the second one is incorrect as well. As is said in the error message, there are too many arguments to ForAll. In your case, it means that the Filter itself has to be used as the iterable Table in the ForAll. In your second formula, the part where you have 

 

mydatasource As mydatasourceRecord,

 

has to instead be

 

Filter(mydatasource As mdsPreFilteredRecord,mdsPreFilteredRecord.UserId="Jonathan") As mydatasourceRecord

 

 

So like this:

 

ForAll
(
     Filter(mydatasource As mdsPreFilteredRecord,mdsPreFilteredRecord.UserId="Jonathan") As mydatasourceRecord
     ,Collect
     (
        mycollection1
        ,{
             FullNameOriginator: LookUp(mycollection2, ID = mydatasourceRecord.'User (Originator)','Person name')
            ,Status:mydatasourceRecord.Status
            ,'User (Originator)':mydatasourceRecord.'User (Originator)'
            ,Subject:mydatasourceRecord.Subject
            ,'Work item instructions':mydatasourceRecord.'Work item instructions'
            ,WorkflowWorkItemClaimed:mydatasourceRecord.WorkflowWorkItemClaimed
            ,'User (UserId)':mydatasourceRecord.'User (UserId)'
            ,'Due date time':mydatasourceRecord.'Due date time'
        }
     )
);

 

 

Check if it helps @akg1421 

View solution in original post

11 REPLIES 11
poweractivate
Most Valuable Professional
Most Valuable Professional

@akg1421 


@akg1421 wrote:

 

//
ForAll(mydatasource As mydatasource,....

 


You have assigned your record scope mydatasource to be identical to the data source scope mydatasource - you gave them the exact same name! I do not recommend it.

 

I don't recommend to use As with the identical name as the data source

 

Do it this way.

 

I don't know if it will fix it, but it could be problematic to make the As name identical, so it may be better not to:

 

 

ClearCollect(mycollection1,Blank());
ForAll(mydatasource As mydatasourceRecord,
	Filter(mydatasource,mydatasourceRecord.UserId="Jonathan"),
    Collect(mycollection1,
        {
            FullNameOriginator: LookUp(mycollection2, ID = mydatasourceRecord.'User (Originator)','Person name'),
            Status:mydatasourceRecord.Status,
            'User (Originator)':mydatasourceRecord.'User (Originator)',
            Subject:mydatasourceRecord.Subject,
            'Work item instructions':mydatasourceRecord.'Work item instructions',
            WorkflowWorkItemClaimed:mydatasourceRecord.WorkflowWorkItemClaimed,
            'User (UserId)':mydatasourceRecord.'User (UserId)',
            'Due date time':mydatasourceRecord.'Due date time'
        }
    )
);

 

 

See if this happened to help resolve it. 

akg1421
Advocate II
Advocate II

@poweractivate 

Which of the following is correct:

First:

ForAll(mydatasource;
Filter(mydatasource,ThisRecord.'User (UserId)' = "Jonathan"),
    Collect(mycollection1,
        {
            FullNameOriginator: LookUp(mycollection2, ID = mydatasource.'User (Originator)','Person name'),
            Status:mydatasource.Status,
            'User (Originator)':mydatasource.'User (Originator)',
            Subject:mydatasource.Subject,
            'Work item instructions':mydatasource.'Work item instructions',
            WorkflowWorkItemClaimed:mydatasource.WorkflowWorkItemClaimed,
            'User (UserId)':mydatasource.'User (UserId)',
            'Due date time':mydatasource.'Due date time'
        }
    )
);

gives error "Incompatible types of comparison. These types can't be compared: Text, Table." at:

LookUp(mycollection2, ID = mydatasource.'User (Originator)','Person name')

 

Second:

ForAll(mydatasource As mydatasourceRecord,
	Filter(mydatasource,mydatasourceRecord.UserId="Jonathan"),
    Collect(mycollection1,
        {
            FullNameOriginator: LookUp(mycollection2, ID = mydatasourceRecord.'User (Originator)','Person name'),
            Status:mydatasourceRecord.Status,
            'User (Originator)':mydatasourceRecord.'User (Originator)',
            Subject:mydatasourceRecord.Subject,
            'Work item instructions':mydatasourceRecord.'Work item instructions',
            WorkflowWorkItemClaimed:mydatasourceRecord.WorkflowWorkItemClaimed,
            'User (UserId)':mydatasourceRecord.'User (UserId)',
            'Due date time':mydatasourceRecord.'Due date time'
        }
    )
);

gives error "Invalid number of arguments: received 3, expected 2."

@akg1421 

 

The second one is closer, but the second one is incorrect as well. As is said in the error message, there are too many arguments to ForAll. In your case, it means that the Filter itself has to be used as the iterable Table in the ForAll. In your second formula, the part where you have 

 

mydatasource As mydatasourceRecord,

 

has to instead be

 

Filter(mydatasource As mdsPreFilteredRecord,mdsPreFilteredRecord.UserId="Jonathan") As mydatasourceRecord

 

 

So like this:

 

ForAll
(
     Filter(mydatasource As mdsPreFilteredRecord,mdsPreFilteredRecord.UserId="Jonathan") As mydatasourceRecord
     ,Collect
     (
        mycollection1
        ,{
             FullNameOriginator: LookUp(mycollection2, ID = mydatasourceRecord.'User (Originator)','Person name')
            ,Status:mydatasourceRecord.Status
            ,'User (Originator)':mydatasourceRecord.'User (Originator)'
            ,Subject:mydatasourceRecord.Subject
            ,'Work item instructions':mydatasourceRecord.'Work item instructions'
            ,WorkflowWorkItemClaimed:mydatasourceRecord.WorkflowWorkItemClaimed
            ,'User (UserId)':mydatasourceRecord.'User (UserId)'
            ,'Due date time':mydatasourceRecord.'Due date time'
        }
     )
);

 

 

Check if it helps @akg1421 

@poweractivate 

It's working fine. Collection is created as per requirement. However, it does not seem to be Filtering data for UserId="Jonathan"

@akg1421 

 

Maybe you want the Collection to be iterated on all items but for the final result to be Filtered - if so, then maybe you want it like this?

Filter
(
	ForAll
	(
		 mydatasource As mydatasourceRecord
		 ,Collect
		 (
			mycollection1
			,{
				 FullNameOriginator: LookUp(mycollection2, ID = mydatasourceRecord.'User (Originator)','Person name')
				,Status:mydatasourceRecord.Status
				,'User (Originator)':mydatasourceRecord.'User (Originator)'
				,Subject:mydatasourceRecord.Subject
				,'Work item instructions':mydatasourceRecord.'Work item instructions'
				,WorkflowWorkItemClaimed:mydatasourceRecord.WorkflowWorkItemClaimed
				,'User (UserId)':mydatasourceRecord.'User (UserId)'
				,'Due date time':mydatasourceRecord.'Due date time'
			}
		 )
	) As processedRecord
	,processedRecord.UserId="Jonathan"
)

 

Does the above work better?

 

@poweractivate Nope, your previous reply resolved the issue. 

Moreover, please guide how can I have the data fully loaded in collection before the user starts navigating through screens. Because the datasource is a "dynamics 365" entity and it takes usually 15 to 20 seconds before data is fully loaded and showing in Gallery.

 

I have tried App.OnStart() - Didn't work! I then tried LandingScreen.OnVisible() that also didn't work. What would be the right way to STOP user from navigating before the data is completely iterated and stored in collection.

@akg1421 

 

On the first screen of your app, have a big Label that says PLEASE WAIT.

Have a Timer Control on that same first screen where the big PLEASE WAIT label is, that is repeating each second. Make the Duration be 1000 to do this

Make the AutoStart property to be true

Make the Repeat property to be true

OnTimerEnd of the Timer control, use CountRows to check how many Records are in the Collection you are trying to load into.

 

If it is greater than some number of your choice, use Navigate(MainAppScreen) 

So for OnTimerEnd of the Timer control something like this:

 

If(CountRows(myCollection)>50,Navigate(MainAppScreen))

 

 Otherwise the Timer will auto repeat and check it again in another second.

 

See if something like the above could help as starting point @akg1421 

@poweractivate 

 

It just loops around with timer resetting. CountRows is dynamic, it may never be greater than the number of choice. It's values range from 0 to 50

 

If(CountRows(myCollection)>50,Navigate(MainAppScreen))

 

 

Any solution to this?

@akg1421 

 

Instead of 50 just use 0 - or use a smaller number like 5 or 10 does it work better that way?

Try just 0 for now, it sounds like you don't have so many records right now - so just use 0.

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 | Results 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,980)