@WarrenBelz Sorry, Warren, I am not looking to make things worse. Perhaps I am not quite understanding when you use the term 'fields.' When I hear the term 'fields,' I think input box for a user to enter information. So let me try this again...
1. Dataverse table is called BTS_Projects
2. Relevant columns in the table BTS_Projects are:
a. Project Number which is a number type column
During my trouble shooting, I have tried using this column's logical name instead, cr622_consultingsubcategory, per my interaction with Copilot
b. Consulting Subcategory which I thought was a Choices column (but maybe I should be calling this a Lookup column?)
And Consulting Subcategory is synced with the choice Type of Consulting:
3. Then, I have a screen in PowerApps called scrIntakePrintCover,
a. There is a Label on this screen called, coverType
This Label displays whether or not the project is consulting work, corporate tax, valuation work, or regular bookkeeping.
The Text property of this Label has the following code, and works fine:
LookUp(BTS_Projects, 'Project Number' = Value(coverProjectNumberDATA.Text), 'Type of Project')
b There is a second Label on this screen called, print_Consul_subcat_DATA
This Label will display the subcategory of consulting work, if coverType displays the text "Consulting."
It does this by grabbing the project number displayed in the Label, coverProjectNumberDATA, and looking
that up in the table BTS_Projects, to find the corresponding data entered into the column, Consulting Subcategory.
It is this Labels code that I need assistance with. Originally I tried using the following code in the Text property:
LookUp(BTS_Projects, cr622_projectnumber = Value(coverProjectNumberDATA.Text),'Consulting Subcategory')
But that code seems to trigger the error message, "Invalid data from the network"
I thought perhaps the code for coverType would work here, instead pulling 'Consulting Subcategory' data;
however, the difference here is that this involves a Choices column type.
I hope I did a better job of communicating the relevant fields, and again, thank you for taking the time. If you think I have missed including any other relevant field information, let me know.
Best,
Kristine