Issue Description: What’s happening?
When executing an UPDATE on a Table with a required smart field of type phone, the update input labels the smart field as required for the mutation.
Reproduce the Issue: What steps can someone take to replicate the problem?
- Create a Table
- Add a required smartphone field and another field
- Create some records
- Try to update the other field without sending the smartphone field
Expected Behavior: What did you expect to happen?
Update type shouldn’t require to send mandatory fields
Actual Behavior: What actually happened?
It was requesting the phone number smart field