cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jja
Post Prodigy
Post Prodigy

Production management model driven app scenario

Hi

I am building a production management model driven app

Can you help me how do i achieve it

in one table i have productions project registrations(Projects)

Other table holds products what will be produced in that particular project(Details)

Every product must undergo 5 stages before it is finished

User will record the start and end stage of each product

My question is where to define stages lets say stage1,stage2 stage3 etc. and stage start and end date? does it have to be in same table as products(Details) or for that better to define separate table and record each transaction(stage1 startdate, end date, stage2 stard date end date , etc)

 

About registering stages of a project products how do i achieve this?

User selects project and gets listed all products that are within that project and sees stages and can check mark a stage and input start and end date of each stage?

1 ACCEPTED SOLUTION

Accepted Solutions
v-jefferni
Community Support
Community Support

Hi @jja ,

 

IMO, the Details table should be a main table which includes all projects, and Projects table could have items of a selected project along with its details which are stages and dates. There need be a one to many relationship between the Projects table and the Details table. But the premise is the 5 stages are all the same in all of the products. In Model-driven app, the main form should be the Projects table and users need to select a project from the Details table and decide the statements of the 5 stages. You could also append business rules to autofill the start date and end date base on the time of first/last stage changes status.

 

Hope this helps.

 

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

View solution in original post

1 REPLY 1
v-jefferni
Community Support
Community Support

Hi @jja ,

 

IMO, the Details table should be a main table which includes all projects, and Projects table could have items of a selected project along with its details which are stages and dates. There need be a one to many relationship between the Projects table and the Details table. But the premise is the 5 stages are all the same in all of the products. In Model-driven app, the main form should be the Projects table and users need to select a project from the Details table and decide the statements of the 5 stages. You could also append business rules to autofill the start date and end date base on the time of first/last stage changes status.

 

Hope this helps.

 

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Helpful resources

Announcements
Power Apps News & Annoucements carousel

Power Apps News & Announcements

Keep up to date with current events and community announcements in the Power Apps community.

Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Power Apps Community Blog Carousel

Power Apps Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Top Kudoed Authors
Users online (4,961)