Dataverse Record Retrieval

[Base2Rob]

Hello all, hoping to get some guidance on what I thought would be a simple task. @RandyHayes, I saw one of your posts that was close to this issue, but not quite the same. 😊

The objective is to retrieve a single record from a Dataverse table, as a local collection using the pattern below (silly data sample). As expected, the Lookup returns a Table with a single record constrained by value provided in the Name field.

// Make some beagle data to have something to work with...
Collect(colDogs,
    {Name:"Dizzy",Breed:"Beagle",Age:"5",Color:"Tri-Color"},
    {Name:"Miles",Breed:"Beagle",Age:"4",Color:"Tri-Color"},
    {Name:"Ella",Breed:"Beagle",Age:"5",Color:"Tri-Color"},
    {Name:"Louis",Breed:"Beagle",Age:"2",Color:"Tri-Color"}
);

// Get a beagle record...
Set(selectedDogRecord,
    LookUp(
        colDogs,
        Name = "Miles"
    )
)

Here's the trouble: When I apply this pattern to a Dataverse table, the record is indeed returned (including all fields), but the only fields with data in them are the constraint column in the lookup and the unique identifier column (prefix_tablenameid). What am i missing?

[AJ_Z]

This is super odd I use this all the time. I even tested using your dummy example

Just checking over the first steps i do when i see this to try and identify the issue.

ensure i am doing Set(selectedDogRecord,LookUp(colDogs,Name = "Miles")) and not Set(selectedDogRecord,LookUp(colDogs,Name = "Miles").Name)

try specify specific columns to show and see if that effects the result:
Set(selectedDogRecord,LookUp(ShowColumns(colDogs,"Age","Breed","Color","Name"),Name="Miles"))

i also save the app come out and go back in that resolves a bunch of funny issues i have.

then i think about the datasource

are those columns truly populated

am i looking up to a collection or gallery with a filter on it or directy to the datasource. 

I also next look at the lookup

try put it in a gallery are there vallues or a label and add .Name at the end or .columnname to see if the lookup part is the problem.

let me know how this goes

[Base2Rob]

@AJ_Z Thanks for looking at this. I checked each of the items you mention (all good practice) - and yes, the columns are populated. I can surface the table in a gallery and see this. I can also export the Dataverse table to CSV and see it as well.

Trouble I'm having is pulling in a single record from the DV table with that single record showing data for all columns.

[Alex_10]

@Base2Rob 

I think your Dataverse table's Default 'Public View' affects on that ( need to add all columns you want to see to that view and publish it )

[Base2Rob · Accepted solution]

I discovered the culprit is Explicit Column selection. Although in preview, it is turned on by default regardless of whether you have created a new app, or have an app that has been in production for a while.

When enabled, unless you explicitly identify the columns to return, it will constrain the return result to (a) the GUID for the record and (b) the column you used to find the record. MSFT is providing the feature to enhance performance, I think.

Turn the feature off to be able to return the entire record, with all columns provided implicitly. Note this can cause issues with existing apps connected to SQL, Dataverse, etc. where a lookup for example returned all columns implicitly, then MSFT enabled the feature and now the lookup will only return the two columns I mentioned.