Error opening edit form
Hello,
our environment:
SharePoint Online
Forms Designer Version: 3.1.5
My problem / question:
I have created forms for a list with the Forms Designer. That works well. Within the forms is no JavaScript code / CSS included.
If I click on the "Edit Item" button in the display form, the error appears: Error 404 NOT FOUND.
The URL for the error is:
https://xxx.com/site/~list/fd_Meldung_E ... 1&List=xxx
Striking is "~ list".
If I replaced "~ list" with "lists/listname", it works.
If I open the edit-form from the list, it will work.
We use the modern design. Is it possibly because of it?
On another page with Forms Designer forms, where no modern design is used, it works.
In "development mode - F12" no errors are displayed.
Many thanks for your help!
our environment:
SharePoint Online
Forms Designer Version: 3.1.5
My problem / question:
I have created forms for a list with the Forms Designer. That works well. Within the forms is no JavaScript code / CSS included.
If I click on the "Edit Item" button in the display form, the error appears: Error 404 NOT FOUND.
The URL for the error is:
https://xxx.com/site/~list/fd_Meldung_E ... 1&List=xxx
Striking is "~ list".
If I replaced "~ list" with "lists/listname", it works.
If I open the edit-form from the list, it will work.
We use the modern design. Is it possibly because of it?
On another page with Forms Designer forms, where no modern design is used, it works.
In "development mode - F12" no errors are displayed.
Many thanks for your help!
- Nikita Kurguzov
- Posts: 889
- Joined: Mon Jul 03, 2017
Dear RMIC,
Please, make sure that Forms Designer app is installed on the site from the store. If it's not installed, you might still be able to customize forms, but there could be errors like this and even more significant ones. Look in Site Contents and make sure Forms Designer is present.
This issue might also appear if the site is created from template, especially if the template used an older version of Forms Designer. Let us know if this is the case or not, we might be able to help.
Please, make sure that Forms Designer app is installed on the site from the store. If it's not installed, you might still be able to customize forms, but there could be errors like this and even more significant ones. Look in Site Contents and make sure Forms Designer is present.
This issue might also appear if the site is created from template, especially if the template used an older version of Forms Designer. Let us know if this is the case or not, we might be able to help.
Cheers
- Nikita Kurguzov
- Posts: 889
- Joined: Mon Jul 03, 2017
Dear RMIC,
Okay, I see. Please, try to open your site in SharePoint Designer, go to All Files, find and delete FormsDesignerAppLib folder.
Next time you connect to the site with Forms Designer, it should recreate this library from scratch and this should fix the issue.
So, please, try to delete FormsDesignerAppLib and then connect to the site, for example, to the same list as before. You can re-save the Display Form as well, but this shouldn't affect the result, as long as you follow the described steps, you shouldn't experience the issue anymore.
Okay, I see. Please, try to open your site in SharePoint Designer, go to All Files, find and delete FormsDesignerAppLib folder.
Next time you connect to the site with Forms Designer, it should recreate this library from scratch and this should fix the issue.
So, please, try to delete FormsDesignerAppLib and then connect to the site, for example, to the same list as before. You can re-save the Display Form as well, but this shouldn't affect the result, as long as you follow the described steps, you shouldn't experience the issue anymore.
Cheers
- Nikita Kurguzov
- Posts: 889
- Joined: Mon Jul 03, 2017
Dear RMIC,
Yes, it seems that one of the files didn't function properly. We've noticed this in our tests and released a micro update, so once the new library was created, the issue was fixed. Thank you for notifying us about the issue!
Yes, it seems that one of the files didn't function properly. We've noticed this in our tests and released a micro update, so once the new library was created, the issue was fixed. Thank you for notifying us about the issue!
Cheers
-
- Information
-
Who is online
Users browsing this forum: No registered users and 21 guests