Table Quick edit Mode Required_if Condition

[ChristianLi]

As a reference to my Communit Q&A post  and verified by @WillowMobileSys 

Required_if Condition is ignored by Quick Edit mode on a table view.

The idea is you have a Parent Table with a selected list of items; Upon saving it creates a series of rows on a child table and  then jumps to its Inline view with Quick Edit activated. The Goal of this work flow is to fill all record on the Parent and child table with no blanks after finishing the work flow.

Yes, ticking the Required box is the solution. However when creating a child row from a parent table you can only extract the Parent ID and the Item name. The child record on the other hand has some more records to be filled up, which cannot be extracted from the parent table. Hence a required_If condition.

One solution to this is by adding a ChangeCounter on the child row. Upon the initial creation of the Row it has a 0 value on ChangeCounter. Upon Creation it will have 1 value on change counter. This 1 ChangeCounter value is then the Required_if. [If ChangeCounter >=1]

Ideally it works. The child row is created with ease. the Required_If condition works when you edit the row is detail view. HOWEVER in Quick Edit Mode the required_If isnt working

I Hope this just a minor issue and ideal use case can be endless.

[Marc_Dillon]

To my understanding, what you're asking for is impossible. I'll try to explain:

-----------

Requirements don't actually force the user to fill anything out, they simply disallow the saving of a Form view if certain things are not filled out, any user can still simply choose to not use the app.

In other words, required_if only affects the ability to save a form, nothing else. With quick-edit, you're not even using a form, so obviously it would have no effect.

Additionally, quick-edit also only works on only 1 column at a time. You can't say something like "if col 1 equals x, then col 2 is required", because they would be filled out in separate quick-edit events, with nothing in between preventing the user from doing something else entirely (like closing the app).

-----------

Generally, I'd say that you shouldn't be using quick-edit if you have this sort of requirement.

Or a possible solution here would be to disable a certain action that continues the workflow, until after all columns have values. For example your child records maybe would start with a [status] of "Pending", and you have an Action button that moves the [status] to "Complete", but is only available once all of the columns are filled out.

-----------

If you don't agree with my assessment of this feature's viability, then I'd love to hear how you envision such a thing working.