Answered

Exporting/Importing a custom SharePoint list form from one list to list with a different name

(1) Share

Report

Posted on by CU05081146-2

Hi,

I have tried the well documented approach of exporting the .zip file package, modifying the JSON and then importing it, this works to an extent, but in my scneario, the lists all exist in the same site and will have different names. When trying to import it, all the controls need to be updated to point to the new data source (with a different list name) and even now, with no errors showing on the form designer, I get some strange behaviour. Basically the form only displays the first item in the list when editing an existing item.

This brings me to the "SharePointForm1" screen and the Item property with the formula

If(IsBlank(SharePointIntegration.Selected),First([@'NewListName']),SharePointIntegration.Selected)
 
In the health checker I have a few errors around the SharePointIntegration element
 
But clicking on them doesn't take me to the problem which I think is where I'm hitting an issue. These are presumably hidden properties.
 
Can anyone help with this please? Would much prefer to resolve this for my own sanity, even if it isn't actually quicker than recreating the form 50+ times.
 
Thanks in advance

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Jon Unzueta 1,834 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
@CU05081146-2

⚠️ Why It’s Breaking After Import
When you export and re-import a .zip package and point it to a new list with a different name, the SharePointIntegration control may not fully rebind to the new list. This causes:

SharePointIntegration.Selected to return empty or null.

The form to default to the first item in the list, even when editing an existing item.

Errors in the App checker that don’t link to visible controls, because SharePointIntegration is a hidden system control

2🛠️ How to Fix It
✅ 1. Use SharePointIntegration.SelectedListItemID Instead
Instead of relying on SharePointIntegration.Selected, use this pattern:
LookUp([@'NewListName'], ID = SharePointIntegration.SelectedListItemID)
This explicitly fetches the selected item by ID and is more reliable after import

.
✅ 2. Rebind the Form Properly
After import:

Go to the SharePointIntegration control (you can find it in the Tree View under “App”).

Reconfigure its properties (OnEdit, OnView, OnNew, etc.) to ensure they reference the correct form (e.g., EditForm(SharePointForm1)).

Double-check that the DataSource of SharePointForm1 is set to the new list.

✅ 3. Reset the Form on Success
Ensure your OnSuccess property of the form includes:
ResetForm(SharePointForm1); RequestHide()
This ensures the form resets and closes properly after submission
1🧠 Additional Tips

If you're importing the form into the same site but with different list names, consider using environment variables or component libraries to reduce manual rework.

For large-scale reuse (50+ forms), it might be worth exploring custom form templates or Power Apps component framework (PCF) for more scalable solutions.

🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

WarrenBelz 154,799 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @CU05081146-2,

Rather than the ChatGPT-generted response below that you have (which does not address the actual core issue of the "hidden" code - you can see it in the error SelectedHidden - specific to the SP List the Form was created on), please have a read of this blog of mine.

In addition to this process, you will need to use the Search (bottom icon on the left) after this and replace all of the references to the original list with those of tne new one.

Happy to elaborate, but if you follow the steps, you can copy any form or screen to anywhere.

Please click Does this answer your question 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 a Like.
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
CU05081146-2 10 on at

Like (0)

Report
Copy link

Link copied!

Thanks @WarrenBelz for the useful information. This copying and pasting method seemed to just give me the same issue as before, but the Search and Replace to update all the references to the source list and replace them with references to the new list was the final piece of puzzle so that seems to be the solution.

Pity Microsoft can't make this a bit of a cleaner process that would help non-developer users to do this.

Was this reply helpful? Yes No
CU05081146-2 10 on at

Like (0)

Report
Copy link

Link copied!

@Jon Unzueta Thanks for the response. Whilst this did resolve the specific issue, as @WarrenBelz said, his solution addresses the core issue and makes the "copying" issue a lot easier.

Was this reply helpful? Yes No