I’m working on an application that will keep various types of records that vary from adding or editing two entities (name and uploaded document) to a user added either by searching through the database (either using a modal dialog or auto-fill) or manually entering at least 7+ entities. All of the entities won’t be displayed to the user in the data grid.

I know there isn't a best way of adding or editing data and varies based on how much information is used to create the one record. I wanted to use two of the methods from this post to create or edit records: What is the best UX to let user perform CRUD operations?

For records with 7+ entities, I wanted to use a modal dialog; while for the records where all the fields were showing, use inline record editing.

Is it a bad practice to use inline editing/sorting on one data grid for one type of record on a separate tab or page, and then to use a modal dialog to either add or edit another type of entity?

I’m working on an application that will keep various types of records that vary from adding or editing two entities (name and uploaded document) to a user added either by searching through the database (either using a modal dialog or auto-fill) or manually entering at least 7+ entities. All of the entities won’t be displayed to the user in the data grid.

I know there isn't a best way of adding or editing data and varies based on how much information is used to create the one record. I wanted to use two of the methods from this post to create or edit records: What is the best UX to let user perform CRUD operations?

For records with 7+ entities, I wanted to use a modal dialog; while for the records where all the fields were showing, use inline record editing.

Is it a bad practice to use inline editing/sorting on one data grid for one type of record on a separate tab or page, and then to use a modal dialog to either add or edit another type of entity?