Jack, I've been doing this for years, as I had an old MCF Gantt app before the integration to QB last year.
l'm utilizing my Gantt App from several 'source' apps.
In each source app, I have the following fields
Logic is relatively straightforward, if they need a gantt, they check the [Use MCF Gantt Flag]. This displays the section containing all the other stuff.
[Create MCF Gantt Project] -> sets [MCF Gantt Project Created Flag]=true -> fires pipeline to add a record containing, as you say, all the pertinent info plus a 'hardcoded type' to a new MCF Gantt record. Once Created, pipeline echoes back the new Gantt.[record ID#] to [MCF Gantt Record].
Once [MCF Gantt Record] is populated, I show:
[Launch MCF Gantt Button] &
[MCF Tasks] : just gives a list of the gantt tasks in the source app for easy viewing/reference.
In MCF Gantt: The following fields
The create Gantt Pipeline populates the [Source Record ID] and sets the [Source App Flag] - Admittedly mine is poor for scalability, could use these 3 fields better instead of replicating them for every app linked to this Gantt app.
[Go Back to Source App] : When Gantt chart UI closes, is drops you in that Gantt app, so for the relatively seamless feel you want, in the main page of Gantt, where I land when closing the UI, I have 2 buttons, reopen the Gantt, or go back to the source.
Mine works well for what I'm doing, let me know if you have any questions!
Good Luck!
Jeremy,
Wow -- thank you. The great news here is that -- as I suspected -- this can be done, and your solution is exactly what I was hoping to hear could be accomplished. The bad news is that I've now got to figure out how to do it. :) I use developers for bigger projects and quasi-coding activities, but probably like you I often just want to get it done. So, I guess I'm going to have to figure out how to setup pipelines to move the information back and forth. Your explanation is helpful in understanding some of the logic flow, field entries and UI considerations, but figuring out the pipeline will be tough. If you can share anything relative to pipeline structures, I'd be all ears and much appreciative -- but I also understand if that's asking too much. I always try to self-teach, so this might force me to figure out pipelines!
Thank you again -- much appreciated!! Have a great day. Jack
Hi Jeremy,
Thanks again for the information. I worked on this for a couple of hours last night, and although I think after doing more pipeline research I can figure out the pipelines, I'm really struggling with the formula-URL fields and what should go in there, and what the syntax should be. I've tried to read all I can on how to setup formula URLs and spent quite a bit of time with the "Magic Buttons" app -- which was helpful -- but I just don't know enough about what I'm trying to accomplish or how the "language" fo the variables and URLs works. Any additional "URL formulas" for dummies help in this case would be appreciated. Thanks for considering.
Qrew LegendHere is a recent post I did on some URL Formulas 101 tips. https://community.quickbase.com/discussion/using-variables-in-api-url-requests#bm73005436-f5f0-4825-9f0a-01873fe71350
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Hi Mark,
I've seen your posts before and they are very helpful. I'm digesting your URL formulas post now, and am going to try to figure it all out and see if I can get it to work. I greatly appreciate your assistance. Very kind. Thanks and I'll be sure to let you know if I get there!
