Collecting child tables by Filtering (working) vs Collecting from lookup parent table and accessing child -not working properly.

(0) Share

Report

Posted on by Z_Lukowski

216

Hi Power Users,

I have found two ways of accessing my 'application Items':

Table 'Application' have 1:M relationship with application items,

so in #1 approach Im filtering 'Application items' based on lookup table(Application) and its GUID Application.Application, I have this stored in varApplication.Application, varApplication has all the info about my application including 'varApplication.application' which is GUID.

code #1 works and retrieving me all application items

I thought code#2 should works similarly - It Lookup application record with GUID I have stored in varApplication.Application, and after the "." going to look for "Application Items". Well... it does and return same number of records with same GUIDS,

but 'Application Items' I get from this operation are lacking their Lookups..., other data seems to be there. Collection 'ColTestAppItems' kept records with related entities to 'Application Items', (I can sum them later on), but 'ColTestAppItems2 just left those fields blank, and kept no related records, just blanks.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

BCBuizer 22,833 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Filter returns all records that match the criterium, whereas Lookup returns the specified value of the first record that matches the criterium.

A full explanation can be found here:

Filter, Search, and LookUp functions in Power Apps - Power Apps | Microsoft Docs

Was this reply helpful? Yes No
Z_Lukowski 216 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BCBuizer ,
this is not the case, I know my lookup will return only one record with proper GUID, thats why I used Lookup(Application,xxx).'Application items' and that construction returned me 112 records with application items matching my Application.
The lookup youre referring to is without " .'Application items' " which would return only one record.

This is not the issue, because in both cases I have same number of records (in my case 112 'Application items') but in Filter I returned records with all the data, and in Lookup I've got 112 records but without related records in collection.

Was this reply helpful? Yes No
BCBuizer 22,833 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Are the columns for the missing data included but blank for each record or missing all together in the collection?

I can imagine that only the columns for 'Applications' are included since that is the input for table.

Was this reply helpful? Yes No
Z_Lukowski 216 on at

Like
a
(0)

Report
Copy link

Link copied!

@BCBuizer The columns are there, they are blank. Collection is taking everything from 'Application Items' besides lookups from records.
@BCBuizer wrote:
Are the columns for the missing data included but blank for each record or missing all together in the collection?

I can imagine that only the columns for 'Applications' are included since that is the input for table.
'Applications' is not the input, 'Application items' are

Example:
Lookup(Application,AnyCondition) - returns 1 record from 'Application'
Lookup(Application,AnyCondition).'Application Items' - returns ALL records from 'Application Items' connected with Application which is Lookuped.
The only issue is that those 'Application Items' are missing their own Lookups, so If I had a User on this 'Application Item', its now Blank, If I had any non-Lookup field its there (like - Name, GUID etc.)

Was this reply helpful? Yes No