Conditional Pro

[Roselee Kruppa]

Ithought I was missing a save button or this was a bug as well. Being able to save to the main table view would be incredibly helpful for our team rather than creating another view which can clutter our boards.

Agree, we have several staff with their own formatted view of the same table. We want to set conditional coloring to Main Table (once!) and have it reflected in all staffs personalised view of the table. As it stands any updates to main table conditions need to be manauly added to the staff views in the 1st instance and then repeated every time the Main Table conditions are updated.

I want to make sure I'm not missing something. I have an automation that copies some data columns from one table to another, when a button is clicked on an interface. It does this for batches of data, and I have a checkbox to mark when the automation reviewed a record.

This would require using the Conditional Logic tool in automations. However, I can't seem to use both Conditional Logic and Repeating Group. I'd like to 'Repeat' through every record, then use a Conditional Logic by finding if a match exists.

You might also be able to break up your automation into 2 separate automations, but that would require creating an extra table as a "holding tank" for your records to figure out what to do with them. This adds a lot of unnecessary overhead to your base, especially because ANOTHER LIMITATION of Airtable's automations is that you can't delete records (unless you write Javascript code).

Make is a no-code platform that can handle the world's most complex automations, and it can literally do hundreds of thousands of things that you can't do natively in Airtable. And you don't need to know any programming code at all.

Some people might tell you to use Zapier (which has spent a fortune on advertising in the USA), but those people are inexperienced and/or new to the industry, so they truly don't understand what they are recommending. Zapier is SIGNIFICANTLY more expensive than Make, yet it can only do about 0.1% of what Make can do. I wrote an entire post here comparing Make vs. Zapier.

A non-Javascript possibility could be creating a "Tasks" table where it'll create one record per item in the list, and you could have another automation that'll trigger per record with the conditional logic perhaps

I had this exact challenge today and managed to solve it with a very small script that ChatGPT wrote for me in a couple of minutes. I am trying to set country level targets and need to first find the list of all countries, and then review which countries already have targets and create target records for any that are missing.

I then used these as input variables ("Countries" & "Existing_Countries") to the script. The script outputs a new list called "Filtered_Countries" which I used as the input to the repeating group to create the missing records.

Recently we have been migrating to a non-trivial BGP setup, and I have had to experiment with the conditional advertising BGP feature in Palo Alto. I was familiar with this concept from cisco, but alas I still found the documentation available on this feature to be a bit unclear and lacking. So, I've written a how to with a step - by - step scenario in order to help the next person who comes along with the same questions I had.

I would be very appreciative if the community where to check the blog post here and give me their feedback / questions / mistakes that i've made, in order to better the article and hopefully even submit it as a document here on the paloalo knowledge point:

The question I have is, can I make advertising a subnet conditional on the default route? I am thinking that it is possible that I didn't receive default route from my ISP for whatever reason, and then I don't want to advertise my public IP space to them. I know, kind of a weird problem, but just because I have an adjacency doesn't mean that all is well.

We work with the control center, and we have 50 plus sheets of a template sheet. (we have approx 10 templates in the template) We need to change the conditional formatting due to a change in our drop-down lists. As of right now, we will have to do it on every sheet. This is tedious and prone to error. With the changing conditions of our supply chain, I can now see the need for future adaptations, across several of our templates - and a lot more wasted time spent on formating - like weeks at a time. A HUGE pita.

There currently isn't a way to update Conditional Formatting rules through Control Center's Global Update feature. Please let the Product team know about the feedback you've posted above by filling out this form which goes directly to them for review: Product Feedback Form.

In regards to a different strategy with Reports and Dashboards, it's hard to say without seeing your specific set-up and end-goals. If your plan has access to it, I would suggest booking a Pro Desk session under the Control Center category to go through this with someone over screen share.

Also would like to see the ability to word wrap a column as one of the global update changes. If you missed a word wrap in your blueprint, same problem, you have to go edit the sheet in every project (we have 46 so 46 changes).

I opened a support ticket, but I can't close this pop-up no matter what I click or what browser I use and I'm wondering if anyone has any insight. I'm LOCKED OUT of my work because of some stupid UI refresh alert. ?

I currently have conditional formatting set up in grid view where the text in a particular column is a certain color depending on the value. Is there a way that this same conditional formatting will apply and be visible when I switch to calendar view? Currently, all the info is the same color when switching from grid view to calendar view. Thank you for any insights shared!

We have a long dropdown of available courses on a lead capture form, but to make it easier for the user we want to add a controlling property that filters the longer list, e.g. if (controlling property) is 'Course Level - Option 1', it then only shows e.g. 4 of the values in the long dropdown.

"Moving forward, when you manually create a new record or set the property's value on a record or inline on an object home page, the property's available options will depend on the controlling property's value for that record. If the controlling property doesn't have a value, all options will be shown for the dependent property."

As @karstenkoehler mentioned, there is currently no way to use the new conditional properties in forms, you can however split your property into multiple fields and then use the dependant form fields to decide which property to show in the forms. You can then implement a workflow to migrate these separated property values into a singular property. This allows you to ease the process for the end user while still storing all your data in one place. I also suggesting modifying the internal viewing permissions to Super Admins only to not clog up your filters with the additional properties.

I agree. For forms, there aren't any clean workarounds at the moment, unless you're open to adjusting the forms embed code with JavaScript. Separate properties are likely the best option in terms of usability. HubSpot currently does not have any native features for this.

Hello - I'm trying to use the crew macro's "Conditional Runner" tool so that upon the successful completion of one workflow, another workflow is triggered to run afterwards. The workflows I want to run are in a directory, so I used the directory tool as the input.

Alternatively if you only want to kick off workflows if there is a condition that passes records through upstream, you would have the workflow, then a conditional runner, then another runner for each subsequent workflow to execute.

I would suggest rolling up each workflow into a Batch Macro instead and then linking the macros together in a parent workflow. This has the added benefit that they will be supported on Alteryx Server so they wouldn't have to be modified if they are ever published to a private Gallery. The CReW Runner Macros are only supported in Designer.

Hey HubSpot,

We find great value in the "Update Deal Stage properties" feature in HubSpot to standardise data collection. However, there's a challenge when we have deals that are going through our Pipeline/Process that warrant different data to be collected at the same stage.

Currently we have two options,

A) Which is to list out all fields and possibilities at that stage as "unrequired" which isn't user-friendly

B) Split out into separate pipelines which is drastic and affects forecasting (as you can only look at one pipeline at a time).

Summary

Without splitting this out into an identical, yet partitioned pipeline - we'd much prefer it to all sit in the same pipeline, but have functionality by saying if Deal Property is X, then show only Fields Y and Z at this stage.

3a8082e126