Forum Discussion
MCFNeil
8 years agoQrew Captain
Most of the time, it is best to create and connect all these records through a code page, rather than a really long formula url field. Especially if you want those child records to have grandchildren
But that takes some coding, or some help.
But that takes some coding, or some help.
ClaytonRountree
8 years agoQrew Cadet
Hi, so the projects to estimates works just fine, no issues there. When on an estimates record, I want to click a button that creates 34 children on the estimate details table. These 34 records should auto-populate with the details from the estimate record they were created from. The difference between each of the 34 is which team they are assigned to (pre-set list of 34 teams). This way we can track which of the 34 teams haven't responded to an estimate request. Then there will be fields on each of the 34 that each team will manually fill. Does that make sense?
So for Project 1234, we may create a planning phase estimate. The planning phase estimate will need to know how each of the 34 teams will be impacted by the project. Each team will assess their impact on a estimate details record for project 1234 for the planning phase estimate. Later during the execution phase a change request might go out for project 1234. This is a different type of estimate, so the 34 teams will need to respond with their impacts again. Hopefully this paints the picture for you?
So for Project 1234, we may create a planning phase estimate. The planning phase estimate will need to know how each of the 34 teams will be impacted by the project. Each team will assess their impact on a estimate details record for project 1234 for the planning phase estimate. Later during the execution phase a change request might go out for project 1234. This is a different type of estimate, so the 34 teams will need to respond with their impacts again. Hopefully this paints the picture for you?