Hi all
I have been spinning my wheels for a few days now with my code below.
The objective here is to sync records between an external 'source' system and Dataverse. The basic steps are:
I have also posted full part of the code relevant to this issue in the second code snippet.
Issue Summary: Evaluation 2 does NOT result in showing me the records in the source system that are NOT in Dataverse. I have played around with several versions of the expression into 'IsBlank (LookUp' etc etc without success. I have analysed record by record, and show the collections in Galleries side by side and the expression is definitely not showing what I see in the galleries (I.e. I can see I have record ID's in the source where they are NOT in Dataverse).
Now @RandyHayes I know you are going to hammer me about using collections in this way, but from the testing I have done, this scales the performance when dealing with thousands of records (noting delegation constraints). But obviously still happy to hear this and increase my understanding of the platform as I am still very novice.
Any help would be greatly appreciated.
Evaluation 2 Code Snippet:
//Evaluate Records in Source NOT in Dataverse to determine Items to Add
ForAll(
Filter(
colSourceItems,
AccountCode = varSourceAccountRevenueCode
),
If(
!(ThisRecord.ItemID in colSourceItemsDataverse.cr07e_itemid),
Collect(
colSourceItemsToAdd,
{
ItemID: ItemID,
Code: Code,
Name: Name,
Description: Description,
AccountCode: AccountCode,
UnitPrice: UnitPrice,
UpdatedDateUTC: UpdatedDateUTC
}
)
)
);
Full Code Snippet:
Clear(colSourceItemsToUpdate);
Clear(colSourceItemsToUnchange);
Clear(colSourceItemsToInactivate);
Clear(colSourceItemsToAdd);
//Get Product List from Source
ClearCollect(
colSourceItems,
GETItems.Run()
);
//Collect Source Products currently in Dataverse
ClearCollect(
colSourceItemsDataverse,
ShowColumns(
colSourceItemsDataverse,
"cr07e_itemssourceid",
"cr07e_itemid",
"cr07e_name",
"cr07e_code",
"cr07e_accountcode",
"cr07e_description",
"cr07e_unitprice",
"cr07e_updateddateutc",
"cr07e_updateddateutcnew",
"statecode"
)
);
//Evaluate Records in Dataverse to determine Items to Inactivate / Update / Unchange
ForAll(
colSourceItemsDataverse,
If(
And(
ThisRecord.Status = 'Status (colSourceItemsDataverse)'.Active,
ThisRecord.ItemID in colSourceItems.ItemID
),
If(
ThisRecord.cr07e_updateddateutcnew < DateTimeValue(
LookUp(
colSourceItems,
cr07e_itemid = ItemID, UpdatedDateUTC
)
),
Collect(
colSourceItemsToUpdate,
{
ItemsSourceID: ThisRecord.cr07e_itemssourceid,
ItemID: ThisRecord.cr07e_itemid,
Code: Code,
Name: Name,
Description: Description,
AccountCode: AccountCode,
UnitPrice: UnitPrice,
UpdatedDateUTC: UpdatedDateUTC
}
),
Collect(
colSourceItemsToUnchange,
{
ItemsSourceID: ThisRecord.cr07e_itemssourceid,
ItemID: ThisRecord.ItemID,
Code: Code
}
)
),
If(
ThisRecord.Status = 'Status (colSourceItemsDataverse)'.Active,
Collect(
colSourceItemsToInactivate,
{
ItemsSourceID: ThisRecord.cr07e_itemssourceid,
ItemID: ThisRecord.ItemID,
Code: Code
}
)
)
)
);
//Evaluate Records in Source NOT in Dataverse to determine Items to Add
ForAll(
Filter(
colSourceItems,
AccountCode = varSourceAccountRevenueCode
),
If(
!(ThisRecord.ItemID in colSourceItemsDataverse.cr07e_itemid),
Collect(
colSourceItemsToAdd,
{
ItemID: ItemID,
Code: Code,
Name: Name,
Description: Description,
AccountCode: AccountCode,
UnitPrice: UnitPrice,
UpdatedDateUTC: UpdatedDateUTC
}
)
)
);
//Process Items to Update
If(
!IsEmpty(colSourceItemsToUpdate),
UpdateIf(
colSourceItemsDataverse,
ThisRecord.cr07e_itemssourceid in colSourceItemsToUpdate.ItemsSourceID,
{
cr07e_itemid: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
ItemID),
cr07e_code: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
Code),
cr07e_name: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
Name),
cr07e_description: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
Description),
cr07e_accountcode: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
AccountCode),
cr07e_unitprice: LookUp(
colSourceItemsToUpdate,
ItemID = cr07e_itemid,
UnitPrice),
cr07e_updateddateutcnew: DateTimeValue(
LookUp(
colSourceItems,
ItemID = cr07e_itemid,
UpdatedDateUTC
)
),
statecode: 'Status (colSourceItemsDataverse)'.Active
}
)
);
//Process Items to Inactivate
If(
!IsEmpty(
colSourceItemsToInactivate
),
UpdateIf(
colSourceItemsDataverse,
ThisRecord.cr07e_itemssourceid in colSourceItemsToInactivate.ItemsSourceID,
{
cr07e_updateddateutcnew: DateTimeValue(
LookUp(
colSourceItems,
cr07e_itemid = ItemID,
UpdatedDateUTC
)
),
statecode: 'Status (colSourceItemsDataverse)'.Inactive
}
)
);
//Process Items to Add
If(
!IsEmpty(
colSourceItemsToAdd
),
ForAll(
colSourceItemsToAdd,
Collect(
colSourceItemsDataverse,
{
cr07e_itemid: ItemID,
cr07e_code: Code,
cr07e_name: Name,
cr07e_description: Description,
cr07e_accountcode: Value(AccountCode),
cr07e_unitprice: UnitPrice,
cr07e_updateddateutcnew: DateTimeValue(UpdatedDateUTC)
}
)
)
);
Patch(
ItemsSources,
colSourceItemsDataverse
);
Refresh(ItemsSources);
UpdateContext(
{
varSourceProductSyncResult:
"New: " & CountRows(
colSourceItemsToAdd
) & Char(10) &
"Updated: " & CountRows(
colSourceItemsToUpdate
) & Char(10) &
"Inactivated: " & CountRows(
colSourceItemsToInactivate
)
}
);
Solved! Go to Solution.
Hi @Nebulas ,
Firstly try this
ForAll(
Filter(
colSourceItems,
AccountCode = varSourceAccountRevenueCode &&
!(ItemID in colSourceItemsDataverse.cr07e_itemid)
) As aItems,
Collect(
colSourceItemsToAdd,
{
ItemID: aItems.ItemID,
Code: aItems.Code,
Name: aItems.Name,
Description: aItems.Description,
AccountCode: aItems.AccountCode,
UnitPrice: aItems.UnitPrice,
UpdatedDateUTC: aItems.UpdatedDateUTC
}
)
);
As well as the ambiguity issue with the identical field names, it is good to keep the filter together.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
Hi @Nebulas ,
Firstly try this
ForAll(
Filter(
colSourceItems,
AccountCode = varSourceAccountRevenueCode &&
!(ItemID in colSourceItemsDataverse.cr07e_itemid)
) As aItems,
Collect(
colSourceItemsToAdd,
{
ItemID: aItems.ItemID,
Code: aItems.Code,
Name: aItems.Name,
Description: aItems.Description,
AccountCode: aItems.AccountCode,
UnitPrice: aItems.UnitPrice,
UpdatedDateUTC: aItems.UpdatedDateUTC
}
)
);
As well as the ambiguity issue with the identical field names, it is good to keep the filter together.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
Hi @WarrenBelz
Thanks for your super fast response. This set me on the correct path.
Turns out that my issue was some dirty test data from one of my previous versions of the code that erroneously repeated the same ItemID/Name across about 60 records. This was overstating the number of 'unique' records that were going to be 'Updated'. This over statement led me to change my Not In expression. Once I reverted back to my original expression ( !(ItemID in colSourceItemsDataverse) and compared against your version it was actually getting the same and correct results. Now that I have deleted the dirty data, the sync routine now works perfect again.
That being said, it looks like there is merit in using your variation with the 'As aItem' as this will help me better distinguish between field names/datasources especially when nested in ForAll's / LookUps etc that can get very confusing.
Would this be accurate?
Thanks again for you help!
Hi @Nebulas ,
Yes - the As statement is a disambiguation tool - the issue with the original Patch was the identical field names on both sides. It is also good to keep the filter in one statement.
Hi @WarrenBelz
Okay I understand, and this is really going to help me clean up and better differentiate the items within my collections.
So in Summary I have three main collections at play here:
Collections 1 & 3 above would benefit from using 'As aItem' to disambiguate (May have just invented a word).
Collection 2 above is my 'Staging Collection' where I apply each of the outputs from collection 3. I deliberately use identical field names so that the patch statement is simple (I.e. Able to patch the entire 'colSourceItemsDataverse' collection into the Dataverse table because all of the field names match).
Thanks again, this has been a valuable learning exercise that will help me going forward.
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!
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
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.
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