cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Add Columns from SharePoint List2 to Collection for SharePoint List1

I hope someone can help me with this collection confusion. I have an existing collection, colFieldSeparation2, that collects information from one SharePoint list, TestOSCMainv2. I want to add additional columns to the collection from a separate SharePoint list, TestOSCIT. The existing collection, colFieldSeparation2, collects employee information and adds it to a gallery, LookupGallery. I'm collecting information for multiple employees and adding those records to the gallery with the collection. I need to add columns from a second SharePoint list to each employee record that is collected in colFieldSeparation2. I tried to use a ForAll statement with the second list, but it creates a blank row after each record. I also need to patch the records in the collection to both SharePoint lists.

Collect(
    colFieldSeparation2,
    {
        EmployeeID: locCurrentEmployee.Employee,
        EmployeeName: locCurrentEmployee.FirstName & " " & locCurrentEmployee.LastName,
        UnionNo: locCurrentEmployee.Craft & " / " & locCurrentEmployee.Class,
        JobNameNo: locCurrentEmployee.LastJob & " / " & locCurrentEmployee.JobDesc,
        HireDate: locCurrentEmployee.HireDate,
        Position: lblMultPosition.Text,
        UnionType: cbFldPosition.Selected.Value,
        CanRehire: cbFldRehire.Selected.Value,
        DSIEquipment: cbFldEquipment.Selected.Value,
        DSICreditCards: cbFldCards.Selected.Value,
        EquipmentCollected: cbFldEquipCollected.SelectedItems.Value,
        CreditCardType: cbFldCardCollected.SelectedItems.Value
    }
);

ForAll(
    TestOSCIT,
    Collect(
        colFieldSeparation2,
        {
            FormID: ID,
            EmployeeID: EmployeeID,
            EquipmentCollected: cbFldEquipCollected.SelectedItems.Value,
            ReviewVoicemail: cbFldVMAccess.Selected.Value,
            ReviewVoicemailYes: cbFldVMYes.Selected.DisplayName,
            EmailAccess: cbFldEmailAccess.Selected.Value,
            EmailAccessYes: cbFldEmailYes.Selected.DisplayName,
            FileAccess: cbFldFileAccess.Selected.Value,
            FileAccessYes: cbFldFileYes.Selected.DisplayName
        }
    )
);

Patch Statement for TestOSCMainv2
ForAll(
    colFieldSeparation2 As My,
    Patch(
        TestOSCMainv2,
        Defaults(TestOSCMainv2),
        {
            EmployeeID: My.EmployeeID,
            EmployeeName: My.EmployeeName,
            UnionNo: My.UnionNo,
            JobNameNo: My.JobNameNo,
            Position: My.Position,
            CanRehire:cbFldRehire.Selected.Value,
            EquipmentCollected: Concat(cbFldEquipCollected.SelectedItems,Value & ", "),
            CreditCardCollected: Concat(cbFldCardCollected.SelectedItems,Value & ", "),
            HireDate: dteHireDate.SelectedDate,
            NoticeType: rdoNoticeType.Selected.Value,
            SeparationDate: dteDateSeparation.SelectedDate,
            LaborMgr: cbFldLaborMgr.Selected.DisplayName,
            Superintendent:cbFldSuperintendent.Selected.DisplayName,
            Branch: rdoFldBranch.Selected.Value,
            SubmittingSeparation: rdoFldSubmitting.Selected.Value,
            SubmitterName: cbFldSubmitterName.Selected.DisplayName,
            SeparationType: rdoFldSeparationType.Selected.Value,
            SeparationTypeOther: txtFldSepTypeOther.Text,
            SeparationReason: rdoFldSeparationReason.Selected.Value,
            SeparationReasonOther: txtFldSeparationReasonOther.Text
        }
    )
);

oscCollection1.pngoscCollection2.pngoscCollection3.png

9 REPLIES 9
rzuber
Responsive Resident
Responsive Resident

You can add columns to your collection by collecting different kinds of records to it.. but all columns with the same names have to have the same data type as the original definition of the columns collected.

 

The two columns I see that match are EmployeeID and EquipmentCollected columns.. Check to make sure those and any other matching columns have the same data types.

@rzuber ,

Thanks for the quick reply!  I've tried to do a Collect with AddColumns and it still returns an error message.  Can you point me to the correct syntax I should be using?

Thanks!

Patti

rzuber
Responsive Resident
Responsive Resident

@PVLove Your syntax seems to be ok. The error indicates that there is something wrong with one of the column data types in the second Collect() statement.

 

What type of value is in locCurrentEmployee.Employee?

 

What type of value is in EmployeeID?

 

You can see by this image that if you try to first collect a string to a record's EmployeeID in a collection, and then try to collect a number value, you get the same error message.

rzuber_1-1718820663120.png

Now if you collect that same record with quotes around the 1, you get:

rzuber_0-1718821059349.png

 

@rzuber ,

The EmployeeIDSearch, SharePoint list, is used to search and locate employee records using a Search icon with an OnSelect property of UpdateContext({locCurrentEmployee: LookUp(EmployeeIDSearch, Employee = Value(TextIDSearch.Text))}). The locCurrentEmployee.Employee is a number value in the EmployeeIDSearch list.

 

The EmployeeID is a number value in a gallery, AddEmployeeGallery, with the Default of a Text Input set to locCurrentEmployee.Employee.

 

I'm combining all of the information from the locCurrentEmployee collection and some columns from the TestOSCMainv2 SharePoint list to create the colFieldSeparation2 collection. I'm using the colFieldSeparation2 collection to capture employee records and add them to a gallery, LookupGallery.

 

My new requirement is to add additional columns from a third SharePoint list to the colFieldSeparation2 collection in order to include them with each employee record created and stored in the collection. I hope that makes sense.

rzuber
Responsive Resident
Responsive Resident

 

@PVLove I understand. However, when you run Defaults(datasource) it returns a record with all the defaults from that datasource. Are there columns in the data source whose names match those columns already in the collection that have a different data type from the column already defined in the collection?

 

Each and every column you are trying to pull into your collection must have a matching data type for any matching column that was defined in the first Collect() call.

 

Is this the only place you do collecting into this collection? If you remove the ForAll(), do you get an error on the first Collect() statement? If so, it's possible the error isn't in this formula... It could be from a different location.. But if you only collect to this collection in this formula, then focus on the data types for the columns in TestOSCIT.

@rzuber ,

I do apologize for not completely understanding what I'm trying to do and/or say.  But I changed the second Collect statement, and it resolved the error message.  But when I add an Employee record it still adds duplicates in the gallery and then overwrites the first record when I add a second record.  Do I need to create a second collection and then merge the two to retrieve the columns I need from the TestOSCIT list?

Corrected second ForAll:
ForAll(
    TestOSCIT,
    Collect(
        colFieldSeparation2,
        {
            FormID: locCurrentEmployee.ID,
            EmployeeID: locCurrentEmployee.Employee,
            EquipmentCollected: Concat(cbFldEquipCollected.SelectedItems, Value & ", "),
            ReviewVoicemail: cbFldVMAccess.Selected.Value,
            ReviewVoicemailYes: cbFldVMYes.Selected.DisplayName,
            EmailAccess: cbFldEmailAccess.Selected.Value,
            EmailAccessYes: cbFldEmailYes.Selected.DisplayName,
            FileAccess: cbFldFileAccess.Selected.Value,
            FileAccessYes: cbFldFileYes.Selected.DisplayName
        }
    )
);

oscCollection4.png

rzuber
Responsive Resident
Responsive Resident

@PVLove - I think I understand.. You are trying to add information to an employee record that exists in the collection, with more information located in the second location?

 

If that is the case, maybe this will work (I am writing this on the fly, so please check for any typos):

 

ForAll(
    TestOSCIT,
    With(
        {
            _existing: LookUp(colFieldSeparation2, EmployeeID = locCurrentEmployee.Employee),
            _newdata: {
                FormID: locCurrentEmployee.ID,
                EmployeeID: locCurrentEmployee.Employee,
                EquipmentCollected: Concat(cbFldEquipCollected.SelectedItems, Value & ", "),
                ReviewVoicemail: cbFldVMAccess.Selected.Value,
                ReviewVoicemailYes: cbFldVMYes.Selected.DisplayName,
                EmailAccess: cbFldEmailAccess.Selected.Value,
                EmailAccessYes: cbFldEmailYes.Selected.DisplayName,
                FileAccess: cbFldFileAccess.Selected.Value,
                FileAccessYes: cbFldFileYes.Selected.DisplayName
            }
        },
        If(
            IsBlank(_existing),
            Collect(colFieldSeparation2, _newdata),
            Patch(colFieldSeparation2, _existing, _newdata)
        )
    )
)

 

In the action portion of the With() statement, you might be able to get away with just:

 

Patch(colFieldSeparation2, _existing, _newdata)

 

but I didn't test that.

@rzuber ,

Thank you so much for your time and patience.  But I was able to resolve the issue before I got your solution.  I added a LookUp to each new column in the collection.  Now I'm trying to patch the second list and that's not working.  Can you help me with that, or should I post a new request?

Updated Collection:
Collect(
    colFieldSeparation2,
    {
        EmployeeID: locCurrentEmployee.Employee,
        EmployeeName: locCurrentEmployee.FirstName & " " & locCurrentEmployee.LastName,
        UnionNo: locCurrentEmployee.Craft & " / " & locCurrentEmployee.Class,
        JobNameNo: locCurrentEmployee.LastJob & " / " & locCurrentEmployee.JobDesc,
        HireDate: locCurrentEmployee.HireDate,
        Position: lblMultPosition.Text,
        UnionType: cbFldPosition.Selected.Value,
        CanRehire: cbFldRehire.Selected.Value,
        DSIEquipment: cbFldEquipment.Selected.Value,
        DSICreditCards: cbFldCards.Selected.Value,
        EquipmentCollected: Concat(cbFldEquipCollected.SelectedItems, Value & ", "),
        CreditCardType: Concat(cbFldCardCollected.SelectedItems, Value & ", "),
        FormID: locCurrentEmployee.ID,
        ReviewVoicemail: LookUp(TestOSCIT, ReviewVoicemail = cbFldVMAccess.Selected.Value),
        ReviewVoicemailYes: LookUp(TestOSCIT, ReviewVoicemailYes = cbFldVMYes.Selected.DisplayName),
        EmailAccess: LookUp(TestOSCIT, EmailAccess = cbFldEmailAccess.Selected.Value),
        EmailAccessYess: LookUp(TestOSCIT, EmailAccessYes = cbFldEmailYes.Selected.DisplayName),
        FileAccess: LookUp(TestOSCIT, FileAccess = cbFldFileAccess.Selected.Value),
        FileAccessYes: LookUp(TestOSCIT, FileAccessYes = cbFldFileYes.Selected.DisplayName)
    }
);

 

rzuber
Responsive Resident
Responsive Resident

@PVLove Is the second list patching the columns to new records? What is the issue?

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