Component String Inputs not working in Published App

[Mach_GO_GO_GO]

In my app, I have a component that I use about a dozen times throughout as a sort of search bar. I have 2 input-text custom-properties for singular and plural terms for what the user is searching for (ie: "City", "Cities"). 

I've entered these in as required and can see them on each component in Design mode:

However, in the published app my inputs aren't registering, and the variables only show the placeholder entries I've entered on the component design page.

[v-xiaochen-msft]

Hi @Mach_GO_GO_GO ,

Could you tell me:

Do you have two textinput controls in the app?

Do you want to pass the content entered in the textinput control to the component?

If my assumptions are correct, I've made a test for your reference:

1\ Create an input custom property “ItemTermPlual”. Its data type is “text”.

2\ Insert a label control and set its Text property to:

Component1.ItemTermPlual    // Component1 is my component’s name

3\ Add the component to the app

4\ Add a textinput control

5\ Set component1_1’s ItemTermPlual property to:

TextInput1.Text

6\ The result is as follows:

 

Best Regards,

Wearsky

If my post helps, then please consider Accept it as the solution to help others. Thanks.

[Mach_GO_GO_GO]

Thanks for the response. Let me re-describe the problem in more detail. 

I have a component in my app called 'Component_ItemSelector' which I use throughout my app as a combination search-input and selection display, somewhat like a combo-box. The user types their query into a text input on the component, which is then passed to wherever it needs to go, usually a gallery, where they make their selection from a list. Once the user has made that selection, it displays the result on the component with the icons to remove the selected item or navigate to a separate screen where that item can be maintained. If nothing came up for the search, an icon appears directing the user to the screen where they can add the item. All these functions are used several times throughout the app, hence using a component for this instead of a combination of combo-boxes and buttons. 

Because this component is used throughout to search different things, I have 2 custom properties on the component called 'ItemTermSingular' and 'ItemTermPlural' to let the user know what to enter in that field. These values gets passed to the 'hint text' property of the text-input on the component side, as well as the tooltip for some of the icons.

The placeholder text for these in the component is "Singular" and "Plural" respectively. 

If the component instance is used to select a city, I input the singular and plural term - 'city' and 'cities'.

Pictured below is the app with 2 component instances on one screen- one for Customer and one for Locations:

So if the user searches for a customer that hasn't been entered yet, the tooltip would read something like "This wasn't found in our list of Customers - click here to add it"

In the create-mode of my app (https://us.create.powerapps.com/studio/), all of this functions as intended, as you can see above. 

However, in the published version of my app, my arguments for 'ItemTermSingular' and 'ItemTermPlural' aren't being passed through, and I get the default search term.

I've tried resetting the component using a button, but it didn't solve the issue. They're situated inside Forms, and I can't call Reset(ComponentName) from the OnVisible property of the screen or the OnReset property of the Form - I get an error that the 'Name isn't valid. This identifier isn't recognized'.

The component otherwise works as intended. 

I should also note that this wasn't a problem with previous versions of the app, but I operate mainly in create mode, and yesterday I noticed it on the published version. I would rather not roll back to a previous version and would instead probably opt to add labels to everything, but I thought I'd post it - possibly a bug?

Session ID: 58c87670-17e1-4d71-b5d3-3562146688cd
PowerApps 3.20114.22

[v-xiaochen-msft]

Hi @Mach_GO_GO_GO ,

Thanks for your reply and happy holiday.

According to your description, I noticed that the user enters information in the component.

So I think what you need is output custom properties instead of input custom properties.

Input custom property is used to transfer data outside the component in the application to the component.

Output custom property is to transfer the data in the component to the outside of the component.

In the example of my previous reply, I used Input custom property. I entered a string outside the component and received it inside the component through Input custom property.

I don't know if the problem is here, could you check it again?

Best Regards,

Wearsky

[Mach_GO_GO_GO]

Not the problem. All I am trying to do is get a string of text I've entered as an input property of my component to display within the component, which is not happening. 

[v-xiaochen-msft]

Hi @Mach_GO_GO_GO ,

So could you tell me:

Do you have an textinput control outside the component? After the user enters the information, is this information passed to the component?

If my assumption is correct, I think the example in my first reply is similar to yours. Have you tried it? Could it be achieved?

If you can't reproduce my example, I think it may be a version problem or a browser problem.

Looking forward to your reply.

Best Regards,

Wearsky

[Mach_GO_GO_GO]

The property I'm having an issue with isn't a user input property. The solution you've described is already working on the control for the part of it that is a user input property. This is not the solution I'm looking for, I'm sorry.