How can I control the record that is exposed via OData

(1) Share

Report

Posted on by steen.rabol

134

For a customer We have developed a new data entity, the data entity is based on InventTable and then some custom virtual fields.

The entity is used to export data to a 3PL. In D365 we have a setup specifying that only items with specific properties or which is part of a specific ItemGroup should be exposed.

Using the $filter is not what the customer want as that will potential expose all items.

how can we apply the "filter" to the data entity so that only items which is allowed for the 3PL is exposed in the data entity ?

Thanks

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (19)

Answers (1)

Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report
Hi,

If you have group field in the entity, you can add filter the exported data as below:
https://X.XXX.dynamics.com/data/YourEntity?$filter=GroupField eq '3PL'

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
steen.rabol 134 on at

Like (0)

Report

No, the filter in the odata query is not the solution in this case, the customer only want to expose the items that is within the criterias of the setup

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

You can add range on the DataSource of your field in the data entity, make sure to add the range to Data source range not to data entity range.

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Saalim Ansari 666 on at

Like (1)

Report

Hi,

To restrict which records are exposed in your custom Data Entity in D365FO, especially when $filter is not acceptable (as it risks exposing all data), you need to apply a permanent filter on the entity itself by customizing its query or datasource.

Was this reply helpful? Yes No
steen.rabol 134 on at

Like (0)

Report

Hi

Yes, I would also think that I need to modify the query somehow, but when look ing at the available methods that one can override on the entity there is none that looks like it can do what I need.

maybe initializeEntityDataSource() and then do not call super() ?

or do you have an example?

I would not like to have to go down the path to replicate inventtable to another table and then use that as datasource for the entity.

Was this reply helpful? Yes No
Raj Borad 1,428 on at

Like (0)

Report

Hi Steen,

You can try below x++ code in data entity query:

    Query q = super(_queryBuildDataSource);
    QueryBuildDataSource qbds = q.dataSourceTable(tableNum(InventTable));

    qbds.addRange(fieldNum(InventTable, ItemGroupId)).value(queryValue("3PLGroup")); // or use item properties
    return q;

Avoid using 'initializeEntityDataSource()' to block super(), as that may cause unexpected behavior.
I think using a query() is a clean, supported approach that ensures only permitted records are included at the source level, thus never exposed externally. May this approach aligns with security best practices for 3PL integration.

Thanks,

Raj D Borad

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi @steen.rabol,

Did you try to add the range to the Query without code? Can you share your entity data sources?

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
steen.rabol 134 on at

Like (0)

Report

Hi @Raj Borad

Thanks for the suggestion, but in which method ?

There is no query() method on the data entity

@Waed Ayyad

As mention, it is a custom entity that is based on Inventtable, there is a dynamic setup, so using ranges will not work

there is not so much to share, you can simply create a new Data entity, then select Inventtable as base table select 2-3 fields and that's it, as mentioned, the data entity will be used by 3PL to get the list of released items, but the customer does not want all items to be exposed, so therefor there is a setup table where there can be one or more item groups that should be exposed to the data entity

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

You can try to use QueryRangeFunctionAttribute to add dynamic range as in the below link:

https://community.dynamics.com/blogs/post/?postid=cbcc74cf-5163-47db-b27c-7517a9a01bee

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi @steen.rabol,

Did you try my last suggestion?

Thanks,

Waed Ayyad

Was this reply helpful? Yes No