Skip to main content
Question

Multiple editable reports on the same page


I have a list of tasks that I can bring over individually into a report with a "Add Task" button. My issue is that I need to be able to do that for 12 individual months and have each report by month to be editable. The formula for my "Add Task" button is... 

URLRoot() & "db/" & [_DBID_TASKS] & "?a=API_GenAddRecordForm&_fid_381=" & URLEncode ([Entity ID#])& "&z=" & Rurl(). 

What would I need in order to have each months "Add Task" button individual for that month?
This topic has been closed for replies.

Forum|alt.badge.img+14
There are various ways to achieve this, and much will depend on whether you need a calendar year of Task records or a full year of records.  And of course, "when" do you get these created?  Are the Tasks Monthly-based or are they simply 12 records with a Month-value selected?

You can opt for Automations to create your records and then use a Refresh button until all the records have been created.  You can then embed separate Reports showing each Month separately onto a parent-form layout; or you can simply GROUP your Tasks table records by Month (you will need to create a formula to help organize the Months in month-order, rather than alphabetical order.


The display/visibility of your Tasks is secondary to creating them.

I would need a calendar year of Task records by month. Those tasks would be brought in at the beginning of each month. Right now I am bringing over the tasks individually but ideally I want to bring over a set group of tasks and then the individual working the project can modify or cancel a task depending on the work done for that particular month. If I embed separate reports by month onto my form will that allow me to edit each report by month? Thank you for your time!

Forum|alt.badge.img+14
Last questions; are you bringing in these Tasks (monthly) for ALL parent records; or only some?  Would it be easier to pre-load an entire year's worth of Tasks when a parent-record is created; so you do not have to do a monthly update?  If the parent-record no longer needs records; you can simply build an automation to trigger a purge of incomplete child-task records.


I think I understand what you mean. Yes I would like to pre-load a year's worth of tasks at the beginning of the project creation but I still need each months tasks to be editable. For example, January may have a task that is in progress until June but then in June it needs to be edited to complete.Is that where the automation comes in? Not sure if you can see my snippet below...