Unable to get app to save collection to sharepoint list

[Andy-AusKiwi]

Hello

I have tried to use both collect and patch to get my collection saved into my sharepoint list. I no longer get errors when clicking the button to save, I just don't get a row added to the list (I was previously getting errors that column names mismatched which I have fixed), so I know it is seeing my sharepoint list to have been giving me errors previously.

Code on button:

Collect(Current_visitors, Visitor)

Sharepoint list:

Emergency_assistnace_required column is set to yes/no as the data in collection comes from a toggle control, is this correctly setup?

Collection:

I've watched videos on youtube and read many articles (including on here) and am unable to get this to work, any assistance is much appreciated

[WarrenBelz · Accepted solution]

Hi @Andy-AusKiwi ,

I cannot see all your fields or field types, but for Collect to work for creating new records in a list from all the records in a collection, you need to check that: -

• All the field names in the Collection are exactly the same as the target fields in the List (the list can however have extra fields that are not being written to).
• All the field types also have to exactly match the type from the matching fields in the Collection.
• There are no required fields in the list that are not being written with data from the Collection.
• The Collection is not writing any fields that cannot be changed in the List (ID, created, modified are a few).

If you get all of the correct, the Collect should work.

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.

[Andy-AusKiwi]

Thanks for your reply @WarrenBelz, So I did have the "title" column as required which is a default, I've now fixed that, I cant find online how I can find the datatype of the values in the collection but I have found the datatypes of the list as below, I think they are all correct now but still same issue occurs

- All the field names in the Collection are exactly the same as the target fields in the List (the list can however have extra fields that are not being written to). - I have triple checked this and column names are the same (including capitals), Would I not expect to see an error in power apps if this was the issue?
- All the field types also have to exactly match the type from the matching fields in the Collection. - I'm not sure how to check the collection data types but have checked the list data types, Would I not expect to see an error in power apps if this was the issue?
- There are no required fields in the list that are not being written with data from the Collection. - There was but not now (the default title column did get me, but now it's set to not required)
- The Collection is not writing any fields that cannot be changed in the List (ID, created, modified are a few). - I'm not writing to any default columns, All columns I'm writing to are ones I've created

[WarrenBelz]

Hi @Andy-AusKiwi ,

I use this code regularly in quite complex data writes and it works - those are the only checks you should need.

Have you renamed any fields in SharePoint? Also go to View>Collections and make sure all the fields are what you expect to see.

Below is some code that runs on the OnSuccess of a form and populates another list with the crew belonging to the one selected in the new record created. You may get some clues from this as well.

Spoiler

ClearCollect(
   colCrewNew, 
   RenameColumns(
      AddColumns(
         ShowColumns(
            Filter(
               colCrewBulk,
               CrewNo = vCrewSet
            ),
            "FullName",
            "FleetNo",
            "Type",
            "CrewNo",
            "VehicleDtls"
         ),
         "WorkDay",
         vDay,
         "JDENo",
         vJDE,
         "LAFHA",
         vNewLAFHA,
         "JobRef",
         NewWorkForm.LastSubmit.ID,
         "Region",
         vNewRegion
      ),
      "FullName",
      "Title",
      "FleetNo",
      "UnitNo",
      "Type",
      "Role",
      "CrewNo",
      "WorkCrew",
      "VehicleDtls",
      "PlantDesc"
   )
);
Collect(
   PlanningResource,
   colCrewNew
)

[v-xida-msft]

Hi @Andy-AusKiwi ,

Could you please share a bit more about he Patch formula you used in your canvas app?

Based on the needs that you mentioned. I think the combination of Patch function and ForAll function could achieve your needs. I have made a test on my side, please take a try with the following formula:

ForAll(
       Visitor,
       Patch(
              Current_visitors,
              Defaults(Current_visitors),
              {
                 Visitor_name: Visitor[@Visitor_name],
                 Company: Visitor[@Company],
                 Emergency_assistnace_required: Visitor[@Emergency_assistnace_required],
                 ......
              }
       )
)

Please consider take a try with above solution, then check if the issue is solved. Please make sure the data type of columns in your 

Visitor collection could match data type of fields in your Current_visitors SP List properly.

Best regards,

[WarrenBelz]

Thanks @v-xida-msft for the alternative, which I may go to if I cannot solve the question posted.

@Andy-AusKiwi, if you want to Patch, this is probably an easier solution, but I think you can solve the Collect problem with a bit of investigation and this is what I am trying to do for you (as you asked this).

[Andy-AusKiwi]

Well, I don't know what caused the problem, but it is now working, both methods are all of a sudden working (I added a second button to try both at the same time), I deleted my Emergency_assistance_required boolean column in my sharepoint list, made all columns not required and it just started to work.

I appreciate the help from both @WarrenBelz and @v-xida-msft 

[v-xida-msft]

Hi @Andy-AusKiwi ,

Have you solved your problem? Is the solution I provided above helpful in your scenario?

If you have solved your problem, or the solution I provided above is helpful in your scenario, please consider go ahead to click "Accept as Solution" identify this thread has been solved.

Best regards,