So I have created a high-level (HL) marketing campaign intake and approval board which includes the corresponding intake form. I wanted the following fields only to be displayed in the HL board:
Campaign name (item)
Campaign Owner/Team Lead (people)
Start Date (date)
End Date (date)
Status -New Request, Under Consideration, Approved
However, there is more granular campaign information in the intake form like asset specs and placement etc. that I would like to only be reflected/displayed in the lower level campaign specific board and not in the high-level approval board.
Is there a way for me to dynamically display top-level information from the intake form on the high-level board and more granular details about the campaign requirements on a low level board?
The only workaround I have found so far is to:
Step 1 > Starting with the high-level approval board > hide the fields generated from the intake form that I don’t want to see reflected on my high-level approval board and save as a new table view.
Step 2 > Set the new table view as board default
Step 3 > I populate the intake form with all the granular campaign details required and submit form.
Step 4 > The High Level board gets populated with top-line key information for the C-suite to review an approve (as the fields with granular details on the campaign are hidden on this new table view)
Step 5 > Once the status on the high-level approval board changes to ‘Approved’ I use automations to pre-populate the fields in the lower-level campaign board with the granular campaign/project details that were provided in the intake form.
is there not an easier or more sophisticated way to get the same results without jumping through all these steps?
I think I understand your solution. To make sure, let me paraphrase as follows: You have a “high-level” board, which is also an intake form and a pre-approval stage. You use the items on this board to hold (but not use or access) data, which may be used at a later stage (post-approval). Once campaigns are approved, they are moved to your “low-level” board and you make use of the data you have been storing.
If that is correct, I have the following questions/comments:
It seems like a good solution! You have solved your problem and buy the sounds of things, most of your process is automated correctly—and it works for you. Be careful not to complain to much about a solution that works!
These steps do not seem super complicated. They are a solid approach to data architecture and show your understanding. I cannot imagine a more simple approach to this or how you would expect this to be easier to configure. Monday.com is very generalized software. Since it is so multi-purpose, it does require additional config compared to specialized software—this has its pros and cons!
I am not sure about your definitions of “high-level” and “low-level”. Perhaps there is more detail in the hidden data, although I cannot see how it is more granular, given that each item corresponds to a campaign, as far as I understand. Is that not correct? 1 item on your “high-level” board becomes 1 item on your “low-level” board, from what I can tell.
Related to the above, I would normally not even consult to use different boards for this. Since all your items are essentially campaigns, I would recommend keeping them all on one board and using different views, dashboards, and filters to manage your campaigns at different points in their life cycle.
Our Monday form builder app, Easyform, supports Connected Boards questions, allowing you to show the items of Board B as options in a dropdown question in a Board A form:
Other features of our connected boars column are
Limiting selection to a single item
Displaying items from multiple connected boards
Limiting select options to items from specific boards when column is connected to multiple boards
Pro plan feature - item default values support - set default values for connected board columns that are hidden in the form.
In addition to that, we offer:
Upload files to your board’s file columns, with support for:
Allowing only specific file types, such as images or pdf
Limiting the number of files that can be uploaded
Setting a maximum for file size
Manually retrying uploads if some or all of them failed
Set default values for the response item’s hidden group, status, connected board and dropdown columns. To do so, select Item default values from the Settings menu.
Add the item’s group as just another field to the form.
Control the page’s top margin, with the ability to set different values for desktop and mobile. To do so, select Page from the Settings menu.
If you’re interested in creating styled forms that better match your brand and embed perfectly on your web page, you can check out our Monday.com app Easyform and our extensive documentation site.
