New forms are not created when schema is adjusted and redeployed

Gravatar

Hi, so I have an unfortunate issue that is affecting my workflow. I was expect that if I add new entities and re-deploy the app that the client forms would be created for the new entities - but it doesn't :( This is a real problem that I'm hoping the team can speedily resolve - can someone look into this? Thanks

User profile image

Hello There,

Can you please clarify what client forms mean? We manually create both entities and fields as we edit, so what you create is what you put into the form.

Please also check our documentation page on how to work with the schema editor in the application settings: https://flatlogic.com/documentation/working-with-app-edditing-application

Gravatar

Hi Alesia, when an application is built, for example let's say I create entities eg posts which has title and body. When I set that up, it would create a form for clients to login and enter data into that form. However, when I go afterward to edit the app and adjust the schema by adding a new entity let's say 'letters', no client form to enter data is created on the client app.

User profile image

When you add a new entity like 'letters' to your existing app schema, the Flatlogic Generator should automatically update the application to include the necessary forms and CRUD operations for that new entity. If the client form isn't being created as expected, it might be due to a synchronization issue or a need to redeploy the app with the updated schema. Also, be sure to save any changes you make by clicking the Save button.

Please also check our documentation page on how to work with the schema editor in the application settings: https://flatlogic.com/documentation/working-with-app-edditing-application

Gravatar

Hi Alesia, yes I did redeploy and did not find the extra forms, that's why I'm reporting it as a bug, can you get the team to investigate this?

User profile image

Please contact me via email with all your questions: [email protected]

Gravatar

Thanks Alesia! I think I found the problem - this is not a bug. What happens is that after deploying a new content type, you have to log into the app's admin section and add the permissions to read or write for the specific user to be able to view the entity form.

Solved
Cookie Consent

By continuing to browse or by clicking 'OK', you agree to the storing of cookies on your device to enhance your site experience and for analytical purposes. To learn more about how we use cookies, please see our cookies policy.