Cannot enable custom forms after changing content type

Question

We have a document library where we use power apps. After we change the content type of that library, we can no longer enable custom forms. The option appears in settings but is disabled only the "customize in power apps" button is available. If we click "customize in powerapps" we will come to the form with the previous customization still there and working well. We have tried to republish the form and also updated the data source.We can't remake the form because we can't delete it because the delete button is missing.

Anyone encountered the same problem? Is there a solution to this?

Answer 1

Dear Martin,

Welcome to the forum here.

I do a test and it seems that I can't reproduce such an issue. 

In my environment, I create a document content type naming Document 2 Type A and add the columns User Field 3 and User Field 4 and set the content type as the default content type.

Then when I go to the Form Settings, I can see that the option can be activated. I kindly suggest you click on Customize in Power Apps>click on Edit fields in Fields> add the content type fields to the original customized form and then publish the form to the site library to see the result.

Meanwhile, check whether the issue only happens in the specific site library in your environment. If yes and if it is convenient, I suggest you copy or move the data to the new library and use the new library as a quicker fix.

Best Regards,

Cliff

Answer 2

Dear Martin,

Welcome to share any updates when you have time if you need further help on this issue.

Best Regards,

Cliff

Answer 3

Hi Cliff thank you so much for your reply!

I apologize for my poor explanation of the issue.

The error occurs when you have created the form with a content type A, then create a new content type B. Changes all documents in the library to content type B and then deletes Content type A from the document library. I have tested this on two different tenants and get the same result. Here is the flow:

1. Created a new document library
2. Turned on the administration of content types in the library
3. Left the default content type document to remain
4. Created a document with the content type document
5. Created a custom form in PowerApps
6. Created a new content type
7. Changed the content type of the document to the new one
8. Deleted that content type document.

Regards,

Martin

Answer 4

Dear Martin,

Thanks for your updates and information.

I'll need some time to follow your steps you provided to do a test in our environment again. I'll update here as soon as possible.

Thanks for your patience and understanding.

Cliff

Answer 5

Dear Martin,

Sorry for the delayed reply.

I follow the flow you provided to do a test again and I still can't reproduce the issue like what is in your environment. You can check the following screenshots and confirm whether they are what you do in your environment.

First I create a new site naming Source Site and create two document content type naming Document Content Type A bound with Document Content Type A.docx and the site column Text Column 1 and Document Content Type B bound with Document Content Type A.docx and the site column Person Column 1.

I apply Document Content Type A to the document library New Library and customize form in Power Apps as follows.

I apply Document Content Type B to the document library New Library, remove the site column Text Column 1 and Document Content Type A.docx from Document Content Type A, remove the document Document Content Type A-1 created with Document Content Type A in the library and finally remove Document Content Type A from the library.

Then I go to Form settings in Library settings, I can still see the custom form option. After I click on Modify form in Power Apps, the form is still bound with Document Content Type A. However, you can hide the unwanted column, add new columns and re-customize the form to make it bound with the new content type Document Content Type B.

If you don't do like what I mentioned above, welcome to upload some screenshots showing how you do that for our confirmation so that I can confirm whether the issue can be reproduced in our environment as well.

Thanks for your effort and time.

Cliff