NoMongo: Allow Access to 'Manage Custom Fields' Without Existing Fields

[gurramkarthiknetha]

Is your feature request related to a problem? Please describe. Currently, users are unable to access the "Manage Custom Fields" section without creating them first. This can be confusing and may lead to unnecessary steps for users who need to manage fields efficiently.

Describe the solution you'd like Users should be able to access the "Manage Custom Fields" section even if no custom fields exist. This would allow them to create, edit, and configure custom fields without the prerequisite of having existing fields.

Describe alternatives you've considered Displaying a message indicating that no custom fields exist while still providing access to management options. Allowing users to create custom fields directly from the "Manage Custom Fields" section without needing to navigate elsewhere.

Approach to be followed (optional) Modify the UI to ensure that the "Manage Custom Fields" section remains accessible regardless of existing fields. Implement a default state or placeholder UI when no fields exist. Provide clear instructions or an option to create custom fields from within the management interface.

Additional context This enhancement would improve user experience by making the custom field management process more intuitive.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• https://github.com/PalisadoesFoundation/talawa/issues/359

[github-actions[bot]]

Congratulations on making your first Issue! :confetti_ball: If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[gurramkarthiknetha]

@palisadoes please assign this issue I completed this

[xoldd]

@palisadoes This feature is useless. That's why it doesn't exist in the develop-postgres branch. Dynamic fields added at runtime are not meaningful to the server in any way because the server cannot know their business logic at runtime as it does not exist in the server's codebase.

If it's really needed, a simple json type field can be added to a postgres table to hold all the dynamic fields and their data.

[gurramkarthiknetha]

Hi @xoldd and @palisadoes, I have successfully implemented the backend for this component, as there was no existing backend for it in develop-postgres branch. That's why this issue was created. Could you please take a look on my code changes.

[gurramkarthiknetha]

in my local machine it is running successfully

[gurramkarthiknetha]

and frontend part is present in develop-postgres branch .

[xoldd]

@gurramkarthiknetha The develop-postgres branch in talawa-admin has to be migrated to work with develop-postgres branch in talawa api, not the other way around.

[gurramkarthiknetha]

Yes, but there is no backend in Talawa-Admin for the ManageCustomFields component. Without the necessary backend queries and mutations, we won't be able to display the ManageCustomFields card.

[gurramkarthiknetha]

we can't able to change any thing in talawa-admin without the backend

[palisadoes]

Closing. We are going to remove the custom fields feature to simplify the API