Hey @pandigita! I'm here to help you with any bugs, questions, or contributions you have for the project. Let's work together to solve this issue!

To address the issues raised:

1. UI Display for Unsubmitted Rows:

   • Implement a mechanism to highlight rows with validation errors in the UI. This can be achieved by adding a visual indicator (e.g., red highlight) to rows that have not been successfully submitted.

2. Saving Draft Rows:

   • Implement client-side storage (e.g., using browser storage) to save draft rows. This ensures that data is not lost even if the user navigates away from the current view. Alternatively, consider saving drafts in a separate database table.

3. User-Friendly SQL Validation Errors:

   • Utilize the extractDBError function from the catchError.ts file to extract and format database errors into readable messages. This function can help translate technical SQL errors into non-technical, user-friendly language ^[1].

Here is an example of how you can handle SQL validation errors and display them in a user-friendly manner:

import { extractDBError } from 'path/to/catchError';
import { NcErrorType } from 'nocodb-sdk';

async function handleDatabaseOperation() {
  try {
    // Your database operation here
  } catch (error) {
    const dbError = extractDBError(error);
    if (dbError) {
      console.error(dbError.message);
      // Display the error message to the user in a user-friendly way
      // For example, you can send this message as a response in an API
      return {
        error: NcErrorType.DATABASE_ERROR,
        message: dbError.message,
        details: dbError.details,
      };
    } else {
      // Handle other types of errors
      console.error('An unknown error occurred');
      return {
        error: NcErrorType.UNKNOWN_ERROR,
        message: 'An unknown error occurred',
      };
    }
  }
}

Additionally, you can leverage NocoDB's BaseModelSqlv2 class to handle and display validation errors effectively ^[2].

Implementing these changes should help make NocoDB more user-friendly and prevent data loss due to validation errors.

To continue talking to Dosu, mention @dosu.

For now, work around is to use new record by form option for this case.

.
.

And we are going to soon introduce this feature in the grid where data entry for non-standard tables will be possible via only form. Also we are looking at how best to do this at grid as well.