Applying a multiplier to a text input field within a gallery - but from an item in the same gallery

[aaronhowe]

I have just started out with PA and am putting together a basic quotation tool.  My users can select tasks and sub-tasks from a gallery in one screen, then in the next screen they can allocate the time needed to complete each subtask.

However, one of those items is explicitly dependent on another item - so if (in the example below) there is time entered against "Attend Meetings" then there must be a set amount of multiplier time entered against "Minutes/Notes" by default, though it can be overridden if needed.

The problem is I can't seem to work out a way of populating the hours field for "Minutes/Notes" once "Attend Meetings" has been completed and have it update when all of those input fields are coming from the same text input control (Text_StaffHours1).

I tried creating a secondary field which is only visible for the row with the name "Minutes/"Notes" but even then I couldn't work out how to filter only the hours applicable to the "Attend Meetings" line.

In summary, the user journey should be:

• From the previous list of items, select "Attend Meetings" and "Minutes/Notes" from the available options
• In this screen, enter an amount of time for "Attend Meetings"
• Minutes/Notes then automatically populates with a multiplied value of the hours in "Attend Meetings"

Sub-tasks ("Attend Meetings", "Minutes/Notes" etc are within label field Label_SubTaskName

Hours are within text field Text_StaffHours1

Am I asking for the impossible?  Or coming at this with the wrong control types?

[BCBuizer · Accepted solution]

Hi @aaronhowe ,

Referring to controls in a gallery won't work. in your data source you need to add a column per activity for the amount of hours which can be referenced from both inside and outside the gallery.

[aaronhowe]

Thank you!  I guess I need to think about how to patch the data back to the SharePoint list in an OnChange property, then reference it in the default text for the text field, then remove it once it's done... eesh.

It might be easier just to set an alert on the page for the user so they can't proceed until both fields have been manually entered 😂