Merging Two Completely Different Tables
Greetings, I couldn't delete this post so, I am just completely modifying it, for anyone who navigated their way back to this and is thinking, "This isn't what I was looking for". lol I have two...
Forum Discussion
What are the business rules? Pipelines are very good at for this sort of simple Many to Many relationships.
Do the Periods all exist prior to the Project creation? If your Periods are calendar months this is straightforward. If your Periods are unique to the Project, something like stages of varying lengths this is more complicated.
Unfortunately, Pipelines are off the table, otherwise, I believe I would be good to go. I don't have any background on the periods but they are not consistent. Period1 is for 1 month, then the next period is the rest of the year, then the next 2 periods cover a year each, but then the next two periods each cover half a year (6 whole months).
Definitely complicated but, turns out the output just has to have the designated details but does not need to look exactly like that. The only thing I can think of is try to use JavaScript to loop through the records and generate everything but, I am not that skilled with it yet. I would love some suggestions, if you have any.
Those are definitely not standard periods. When the Project is created, you will need to create them for each Project. To use JS you will have to build a Code Page. QB will not let you put it into any of the fields in the tables any more.
Why not Pipelines? They are expensive to use for external integrations but they are free (at the moment) for QB to QB.
You could have the Project Manager create the Periods manually, but that might result in a User revolt.