I need multiple stage power apps.

I hear you! Creating a multi-stage form with different access levels for existing and new items can be tricky, but I can definitely help you with that. Here's a breakdown of your requirements and some solutions:

Requirements:

• Multi-stage form: The form should be divided into 7 stages, with users progressing through them one by one.
• Read-only previous stages: Once a user completes a stage, it becomes read-only and they cannot edit it.
• Default form for new items: New items should start on the first stage.
• Conditional display based on tab value: Existing items should display specific stages based on a tab value (presumably indicating their current status).

Possible Solutions:

There are a few ways to achieve this depending on the platform you're using. Here are two common approaches:

1. Using a Form Wizard or Multi-Step Form Library:

Many web development frameworks and form builder platforms offer built-in functionalities for multi-step forms. These libraries handle user progress, stage visibility, and validation.

Here's a general approach:

• Look for a library or plugin that supports multi-step forms and read-only states.
• Divide your form HTML into separate sections for each stage.
• Use the library's methods to control navigation between stages, make previous stages read-only, and display relevant stages based on tab values.

2. Custom Javascript Implementation:

If you're comfortable with Javascript, you can build the multi-stage functionality yourself. Here's a basic outline:

• Use Javascript to hide/show different sections of the form based on a user's progress (stored in a variable or session).
• Implement validation checks for each stage before allowing users to proceed.
• Use Javascript to disable editing of previously completed stages by making input fields read-only.
• Implement logic to determine which stages to display for existing items based on the tab value (using conditional statements).

Additional Tips:

• Clearly indicate user progress through the stages with a progress bar or stage numbers.
• Provide clear instructions for each stage and what information is required.
• Offer a "Review" or "Summary" page after completing all stages for users to confirm their entries before submission.

Resources:

Here are some resources that might be helpful depending on your chosen approach:

• Multi-Step Form Libraries: Search for "Multi-Step Form Library" for your specific development platform. Popular options include jQuery Steps, Form.io, and Vue.js Wizard.
• Javascript Tutorials: Websites like W3Schools (https://www.w3schools.com/js/) offer tutorials on Javascript concepts like DOM manipulation and event handling.

Feel free to ask if you have any further questions or need clarification on any of these points!

Creating a multi-stage form with conditional visibility and read-only behavior in Power Apps can be achieved using a combination of techniques.

 

1. Setting Up Screens and Navigation:

• Create seven separate screens in your Power Apps application, each representing a stage in your form.
• Use the Navigate function to control navigation between screens based on user actions.

2. Form and Data Source:

• Use an Edit Form control on each screen to capture user input for that stage.
• Connect the Edit Form to a single data source (e.g., SharePoint list, CDS table).

3. Conditional Visibility for Stages:

• Utilize the Visible property of controls to determine which stage is displayed.
• Use a variable or a lookup column in your data source to track the current stage (e.g., "Stage1", "Stage2", etc.).
• Set the Visible property of each screen to an expression like VarCurrentStage.Value = "Stage1" for the first screen, and similar expressions for other stages based on the variable value.

4. Read-Only Behavior for Previous Stages:

• Set the DisplayMode property of controls in previous stages to View. This will make them read-only.
• You can achieve this conditionally using the same variable or lookup column as above.
  • For example, on Stage 3, set DisplayMode for Stage 1 and 2 controls to If(VarCurrentStage.Value = "Stage3", View, Edit).

5. Default Form for New Items and Existing Items:

• To differentiate between new and existing items, you can use a hidden field or a flag in your data source.
• Set the initial value of the variable tracking the current stage based on this flag.
  • If it's a new item, set it to "Stage1".
  • If it's an existing item, use a Lookup function to retrieve the current stage value from the data source and set the variable accordingly.

1. Create Screens:
   - Create multiple screens for each stage of the form.
   - Or use a single screen and group sections for each stage.

2. Implement Navigation Logic:
   - Use buttons or other controls to navigate between stages.
   - On each button's OnSelect property, write logic to move to the next stage and make the previous stage read-only.

3. Make Previous Stages Read-Only:
   - Use the DisplayMode property of controls to make them read-only.
   - Set the DisplayMode property based on whether the current stage has been completed.

4. Handle Existing Items:
   - Use the OnVisible property of screens to fetch and pre-fill data for existing items based on the tab value or any other criteria.
   - Set the Default property of form controls to pre-fill data.
 

It sounds like the type of thing that Microsoft would call a wizard and the solution depends on the UI framework. Is the UI framework Windows Forms or WPF or ASP.Net or something else? The following is a sample for a WPF wizard.

Wizard Sample - Code Samples | Microsoft Learn
https://learn.microsoft.com/en-us/samples/microsoft/wpf-samples/wizard-sample