This video is a savior! Been struggling with a post request. Disbaling API for inputs didnt really help. Thought that should help maintain existing values. This helps. !!
Great video.... BUT...Why doesn't this get talked about in the onboarding sessions? Or why isnt it referenced anywhere when setting up API's. It seems like a pretty important step right? I mean I see VERY few use cases where you would use Xano and wouldn't ever need to update only certain fields of a record. I built my app the wrong way because I never saw this 2 year old video buried in your channel, and when updating records I couldn't figure out why it was deleting the fields I have hidden in the Inputs step. OR at the very least, when "hiding" inputs why not have a message somewhere that states what you say at the 1:00 mark. Hiding Input fields gives you the impression that it wont be changed. A simple message and link to this video would be super helpful.
Hey Matt! Assuming I'm understanding you, this would typically be handled by the front-end (validating date format or in the past). That said, if you needed to pass the date from the front-end for backend validation for whatever reason Xano could definitely handle it.
Yes, there is a variable called "now" in Xano. You can write a conditional to say if example date is greater than or less than (depending on your use case) to now, then do xyz, else... etc.
This video is a savior! Been struggling with a post request. Disbaling API for inputs didnt really help. Thought that should help maintain existing values.
This helps. !!
Great video.... BUT...Why doesn't this get talked about in the onboarding sessions? Or why isnt it referenced anywhere when setting up API's. It seems like a pretty important step right? I mean I see VERY few use cases where you would use Xano and wouldn't ever need to update only certain fields of a record. I built my app the wrong way because I never saw this 2 year old video buried in your channel, and when updating records I couldn't figure out why it was deleting the fields I have hidden in the Inputs step. OR at the very least, when "hiding" inputs why not have a message somewhere that states what you say at the 1:00 mark. Hiding Input fields gives you the impression that it wont be changed. A simple message and link to this video would be super helpful.
This should be configurable at the endpoint level. It's ridiculous.
Thank you so much, this is reeeeeeeeally helpful! I am excited with those new features! Good job guys!
Thanks Michael, great help!
this is awesome 😆 thanks for the great work
What will you do if you really want the description empty? I don't want to set the old value, I want the description empty.
Just make sure the value is enabled in your Edit Record step and provide it a blank string instead. Nice and easy!
It's very helpful thx
Hi, are you able to check if a date is valid or has expired. Create a value for this on a tick?
Hey Matt! Assuming I'm understanding you, this would typically be handled by the front-end (validating date format or in the past). That said, if you needed to pass the date from the front-end for backend validation for whatever reason Xano could definitely handle it.
Yes, there is a variable called "now" in Xano. You can write a conditional to say if example date is greater than or less than (depending on your use case) to now, then do xyz, else... etc.
@@nocodebackend okay this is very helpful. Thank you very much. Which plan do I need to be able to do this in xano?