Got it, and that makes total sense! I’ll get back to you here as soon as I have a working example of the code here. I am about to head out for the day though, so it might take me a bit longer to respond here
Edit :- I though this is a gap in documentation but seems like it’s an inconsistency issue with the API itself.
When I pass null to mutate a single column using change_column_value, I’m getting this error message "message": "Argument 'value' on Field 'change_column_value' has an invalid value. Expected type 'JSON!'.",
The right way in that case is to pass an empty JSON as @AlexSavchuk suggested.
However, to mutate multiple columns, sending empty JSON doesn’t work.
I tested with “Text” column and observed the same behavior. @AlexSavchuk - this may be true for even more column types.
For change_column_value mutation, use an empty JSON to clear out column values.
For change_multiple_column_values if using an empty JSON doesn’t work, try using a null.
Hey @upitchika and @supernova - thanks for your awesome suggestions here! That null workaround is quite cool, and using variables as pointed out is what we suggest in all cases to make your life just a little bit easier.
That said, I really appreciate your insight and troubleshooting here - I’ve already gone ahead and added your notes and feedback about the way this works, as well as the way it’s presented in the documentation to our team. Thank you for helping us improve!