This seems like a nested If job. The first solution that comes to mind is to have if statements that does the concatenation while dropping the empty cells.
But this will get messy if there is more than 1 empty cell at a time.
BR,
Mo
It looks like this formula should produce only a single underscore between {Field 5} and {Field 6}.
So, it is strange that it is producing a double underscore. Do you have underscores in any of the field values?
It also looks like the formula might not be displaying correctly. Do you have asterisks * inside the quote marks? If you want the formula to show on these forums exactly as you type it, format it as a markdown code block.
Here is a concatenation formula that will concatenate seven fields, separating items with a comma and omitting commas where there are empty cells. (Note: it will not work correctly for number fields that contain zero values. That would be a much longer formula.) Perhaps you can adapt this formula for whatever symbol you want to use between items.
Absolutely brilliant! This is EXACTLY what I needed.
This community never seize’s to amaze me!
Stay safe!
One last question.
Is there a a way to “trigger” this formula IF and Only IF a certain word exist in another column?
One last question.
Is there a a way to “trigger” this formula IF and Only IF a certain word exist in another column?
Unfortunately formulas can’t be “triggered,” at least not in the sense of having it only run when you want it to run. Whenever any field used by a formula changes, the formula will recalculate, but only when it calculates can it check the data and operate on it. In other words, the trigger isn’t the specific data itself. The trigger is the fact that the field data was changed.
I’m guessing that you want a formula to run at a certain point in your workflow, and maintain that formula result permanently. To accomplish that, you will need to either use the Scripting block (a Pro workspace feature), enlist the help of an integration tool like Zapier or Integromat, or write custom API code, any of which will do the calculation separately and populate a regular data field (i.e. not a formula field) with your desired result.
Unfortunately formulas can’t be “triggered,” at least not in the sense of having it only run when you want it to run. Whenever any field used by a formula changes, the formula will recalculate, but only when it calculates can it check the data and operate on it. In other words, the trigger isn’t the specific data itself. The trigger is the fact that the field data was changed.
I’m guessing that you want a formula to run at a certain point in your workflow, and maintain that formula result permanently. To accomplish that, you will need to either use the Scripting block (a Pro workspace feature), enlist the help of an integration tool like Zapier or Integromat, or write custom API code, any of which will do the calculation separately and populate a regular data field (i.e. not a formula field) with your desired result.
@Justin_Barrett thank you very much for the clarity. I will definitely looking in to Zappier and Integromat.