Forum Discussion
MarkShnier__You
Qrew Legend
4 years agoHere are some answers.
Set / not set means has a value or does not have a value.
All Quickbase steps are at no charge. By definition, Automations were internal to Quickbase, so there will not be any chargeable steps for a converted Automation.
External Automaton steps are renewed annually. I guess your anniversary date is Nov 18th.
Not being able to see other's Pipelines is a known issue they are working on.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Set / not set means has a value or does not have a value.
All Quickbase steps are at no charge. By definition, Automations were internal to Quickbase, so there will not be any chargeable steps for a converted Automation.
External Automaton steps are renewed annually. I guess your anniversary date is Nov 18th.
Not being able to see other's Pipelines is a known issue they are working on.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
MichaelTamoush
4 years agoQrew Captain
Ahh, I was wondering about set/not set as well. So does that essentially mean we can replace using something like, if [Field A] = ""? To test if something is blank or not blank we can now use set/not set?
------------------------------
Mike Tamoush
------------------------------
------------------------------
Mike Tamoush
------------------------------
- MarkShnier__You4 years ago
Qrew Legend
That is my understanding so far.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- JimHarrison4 years agoQrew ChampionI asked Support and here is my interpretation with embellishment.
The "Set" or "Is Not Set" function is a trigger filter. For example when a field in a record changes from "Set" to "Is not Set" or the converse the Pipeline is triggered and runs.
When a User enters data and saves - the trigger is called and this allows the "Builder" (you) to filter which changes start the Pipeline. This is good because otherwise anytime a change is made all the Pipelines run and that is bad.
Pipelines are all about knowing when data changes and doing a thing. In an effort to limit how often the Pipeline runs, you have to apply filters. In this case "Set" = "Present" = "NOT NULL" and "Is not Set" = "Is not Present" = "NULL" does the thing when the User makes the change and saves the record.
Jim Harrison
Portland, OR
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------