Data in Dropdown is reset in gallery when there are many choices

[RyoIshi731]

Hi I am createing attendance management screen and have query.

There is gallery and when I push save button the data is saved in collection.

Now the issue is when I push save button, the data input in dropdown is reset when there are many choices. (24 choices.)

The phenomenon is as follows.

1. I input 08:30 ~ 09:45 in dropbox,  and push Save button. 

   Name of Textbox is WorkingHourFrom,   WorkingMinuteFrom,  WorkingHourTo, WorkingMinuteTo

2.    The data of WorkingHourFrom,  WorkingHourTo, is reset to 00, while WorkingMinuteFrom,   WorkingMinuteTo remains same.

       The data is saved to gallery properlly.       

 

Could someone tell me about this?

FYI, I would like to post code for onSelect of Save Button.

Patch(
    DetailCol,
    ThisItem,
    {
        WorkingDay: WorkingDay.SelectedDate,
        Employee:ThisItem.Employee,
        ProjectName:ThisItem.ProjectName,
        WorkingHourFrom: Value(WorkingHourFrom.SelectedText.Value),
        WorkingMinuteFrom: Value(WorkingMinuteFrom.SelectedText.Value),
        WorkingHourTo: Value(WorkingHourTo.SelectedText.Value),
        WorkingMinuteTo: Value(WorkingMinuteTo.SelectedText.Value), 
        Note: Note.Text,
        saveBtn: false
    }
);

[RyoIshi731]

@WarrenBelz 

Thank you sir

I modified however, it has still error.

In below picture, Employee text box is marked as green, so I think spelling is not an issue.

Regards

[RyoIshi731]

@WarrenBelz 

So Sorry again and again.

I tried this code and still have error.

Patch(
    DetailCol,
    ThisItem,
    {
        WorkingDay: WorkingDay.SelectedDate,
        ProjectName: {Value:ProjectName.Selected.ProjectCode},
        WorkingHourFrom: Value(WorkingHourFrom.SelectedText.Value),
        WorkingMinuteFrom: Value(WorkingMinuteFrom.SelectedText.Value),
        WorkingHourTo: Value(WorkingHourTo.SelectedText.Value),
        WorkingMinuteTo: Value(WorkingMinuteTo.SelectedText.Value), 
        Note: Note.Text,
        saveBtn: false
    }
);

Not only this I also tried, but same error happens.

ProjectName: {Value:ProjectName.Selected.ProjectName},

error

The dropdown data source is ProjectList as follows.

[WarrenBelz]

@RyoIshi731 ,

Can you please take a small step back and understand your code a bit (I assume you wrote it). It is the same error as ProjectName, so you need to fix it in the same way.

[RyoIshi731]

@WarrenBelz   

Thank you so much for your reply.

Unfortunately both employee and ProjectName issue is not solved.  I guess data type is not different between collection and screen input.  However I don't know how to fix it...

[WarrenBelz]

@RyoIshi731 ,

What is the field type of both of these in your List?

[RyoIshi731]

@WarrenBelz 

Thank you sir, good morning.

The data type

Employee: Person or Group in WorkingDetail in SharePoint List

ProjectName: Single Line of text in ProjectList in SharePoint List.

- WorkingDetail

-ProjectList

I am not sure if this is necessary information, but let me share.

#  Project Name in WorkingDetail lookup ProjectList.

[WarrenBelz]

@RyoIshi731 ,

That explains it all - is there any reason you are using Person and Lookup fields? Are you able to use Text fields instead as getting the additional details necessary to Patch back to them is not straight forward and I am reluctant to send you in that direction unless you fully understand what to do next time.

[RyoIshi731]

@WarrenBelz   Thank you so much for you advice on Saturday sir.

The reason I want to use person is because this screen is not just input but also need to use data analysis purpose.

This is attendant management system and want to analyse project wise spent workload.  So I think I used person.

If people use input, it may cause mistake, for example, today I input "Ryo Ishi" , but tomorrow I may input "Ryo" which is different what I input today. Therefore I used person.  

The reason I am using lookup is project will be increased in the future, and want to manage separately in ProjectList.  The ProjectList may be used in other application.

So my point is that I want to keep consitency of data, therefore I use Person and Lookup.

However I am OK if there is other workaround,  I would really appreciate you if you could tell me workaround.

Do you mean for projectname and employee, I will use textbox and freeinput for user?

Regards

[RyoIshi731]

@WarrenBelz 

Let me confirm your point.

Your advice is that in Sharepoint List, the datatype of employee and ProjectName should be single line of text and

on the screen the textinput is used for these 2 items?

[WarrenBelz]

Hi @RyoIshi731 ,

To patch to a Lookup column you also need to ID of the item in the other list that is being looked up. For a person field, you need (at least) the email address and name of the person. Both these field types are multi-element Tables within the field.

I understand your Lookup logic (although you will find there are many other things you cannot do with them in Power Apps), but a Person field has no quality control of what you are patching to it, so it would not care whether you put Ryo or Ryo Ishi in the DisplayName element.

I have not used either in many years and simply store the data in Text columns, doing the Lookup in Power Apps for the control Items (for Lookup) and using the Office365Users connector if I want other data (Person).

What are the Items of the ProjectName dropdown (and I again encourage you to rename this to something other than the field name).

Your Person field however presents a bigger issue as you need to find the email address of the person typed into a text box with no control over the content. I again encourage you to use a Text field here.