Hello!
Yesterday the new 'Trigger output' property appeared for the first time in the modern Text Input control.
Since then, one of my applications does not work correctly. After several tests, I have found out that it is because the new property introduces at least 2 errors:
1) There is a certain delay even if the property is 'Key Press'. Therefore, if immediately after filling in the TextInput we press a button that takes the value of the TextInput, the saved value is not complete. This delay can be verified by replicating the attached capture.
2) If the property is 'FocusOut' and after writing you press a button, the focus change is not detected. Therefore, if the button takes the value of the textinput to save it, it saves it blank.
These errors cause a critical failure in any application that stores the value of a modern text input. In classic control there is no delay.
Please, an urgent solution!
// Define user details and timestamp once
Set(
currentUser,
{
'@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
Department: "",
DisplayName: User().FullName,
Claims: "i:0#.f|membership|" & Lower(User().Email),
Email: User().Email,
JobTitle: "",
Picture: ""
}
);
Set(
timestamp,
"<b>" & Char(10) & User().FullName & "</b>" & "<br> <span style='font-size:10.5pt'>" & Text(Now(), "[$-en-US]yyyy/mm/dd hh:mm") & "</span> <br> "
);
// Handle Patch Operations
If(
!IsBlank(TextInputTicket.Value),
Switch(
TabListMenu.Selected.Value,
"Message",
Patch(
Helpdesk,
CurrentItem,
{
'Case Comments': timestamp & TextInputTicket.Value & CurrentItem.'Case Comments',
LastComment: TextInputTicket.Value,
'Last Modified By': currentUser,
'Last Comment Made By': currentUser
}
),
"Worklog",
Patch(
Helpdesk,
CurrentItem,
{
Worklog: timestamp & TextInputTicket.Value & CurrentItem.Worklog,
'Last Modified By': currentUser
}
),
"Close",
Patch(
Helpdesk,
CurrentItem,
{
Resolution: timestamp & TextInputTicket.Value & CurrentItem.Resolution,
'Last Modified By': currentUser,
Status: {
'@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id: 4,
Value: "Closed"
},
'Assigned To': currentUser
}
)
);
// Handle Errors and Reset
If(
!IsEmpty(Errors(Helpdesk)),
Notify(First(Errors(Helpdesk)).Message, NotificationType.Error),
UpdateContext({ CurrentItem: LookUp(Helpdesk, ID = CurrentItem.ID) });
Reset(TextInputTicket)
)
);
// Handle Ticket Filtering based on Tab Selection
If(
TabListMenu.Selected.Value = "Close",
Switch(
TabList1.Selected.Value,
"Unassigned",
ClearCollect(TicketsCollection, Filter(Helpdesk, Status.Value = "Unassigned")),
"My Tickets",
ClearCollect(
TicketsCollection,
Filter(
Helpdesk,
('Assigned To'.DisplayName = User().FullName) && (Status.Value in ["Assigned", "In Progress", "Waiting for user response", "Waiting for external resource", "Backlog"])
)
),
"Closed",
ClearCollect(
TicketsCollection,
Filter(
Sort(Helpdesk, ID, SortOrder.Descending),
'Assigned To'.DisplayName = User().FullName && Status.Value = "Closed"
)
);
Notify("Ticket was closed and placed under Closed tickets.", NotificationType.Success, 600),
"All",
ClearCollect(TicketsCollection, SortByColumns(Helpdesk, "CreatedDate", SortOrder.Descending))
);
UpdateContext({ itemSelected: false })
)
'TextInputCanvas.TriggerOutput'.Keypress
I was going crazy the past couple of days trying to figure out what changed! When editing forms and submitting them, sometimes the last field to be edited would not be saved. Galleries filtered by text input would not filter in real time as text was typed. I did not notice the same behavior with classic controls and was about to convert the whole project to them.
Thank you so much!
According to https://learn.microsoft.com/en-us/power-platform/released-versions/powerapps-studio-players/3.24064
"For Modern Text Input control, a property called TriggerOutput is replacing old property called DelayOutput. The default value is set to "Focus out" for best performance. This will impact current implementations when opened in studio."
So DelayOutput is replaced.
Setting Blank Trigger output also fix the issue according to my tests.
The first point I mentioned "1) There is a certain delay even if the property is 'Key Press'." I think it's solved, now there's no delay.
Hi there, I also have this issue. There used to be a different property for delaying output. Now you have to click off of the modern text input control in order to get the value of the text input.
Setting the Trigger Output property to "FocusIn" fixed the problem for me.
I took a guess at what values would be accepted since the MS documentation for Modern UI still has...
DelayOutput - When set to true, user input is registered after half a second delay. Useful for delaying expensive operations until user completes inputting text such as for filtering when input is used in other formulas.
Please let me know if this fixed your issue.
Stay up to date on forum activity by subscribing.
stampcoin
10
danielleh
2
WarrenBelz
2
Most Valuable Professional