The view query has been overridden because of a conflict. New extension points.

Warning: The view query has been overridden because of a conflict.

Occurs when users navigate to a page where the corresponding menu item has a query defined for the page. In this case, if the default view also contains a query, the page loads using the default menu item query instead of the default view's query, and the user sees this warning message above.

To resolve this Microsoft created two additional extension points (development required):

• EnableSavedViewQueryPriority - this will use a query saved by the user
  
• OnFailureQueryPersonalizationApply - this gives the ability to merge the queries

The method should be called on the form init() method before super():

[ExtensionOf(formstr(CredManTable))]
final class VKCredManTableFrm_Extension
{
    public void init()
    {
        this.GetFormRunPersonalizationSettings().EnableSavedViewQueryPriority();

        next init();
    }
}

If you want to make that behavior global for all forms or the init method is not hookable (like in the case of the CredManTable form), FormRun can be extended:

[ExtensionOf(classStr(FormRun))]
final class VKFormRunCls_Extension
{
    public void init()
    {
        if (this.form().name() == formstr(CredManTable))
        {
            // per specific form
        }
        // global
        this.GetFormRunPersonalizationSettings().EnableSavedViewQueryPriority();
        next init();
    }
}

A part of the FormRun class and therefore available on the form element level. Definition from FormRun:

    /// <summary>
    /// Extension point used as a fallback method when saved view's was unable to apply query personalizations due
    /// to conflicts with the form's query.
    /// </summary>
    /// <param name = "_sourceQuery">Query object with saved view query personalizations</param>
    /// <param name = "_targetQuery">Query object to be executed</param>
    /// <returns>Method has performed any modifications to the form's query</returns>
    [Replaceable]
    public boolean OnFailureQueryPersonalizationApply(Query _sourceQuery, Query _targetQuery)
    {
        return false;
    }

Called from FormRunConfigurationClass.mergePersonalizationQuery()

Example to transfer all user defined filters with possibility to add exclusions:

    /// <summary>
    /// Extension point used as a fallback method when saved view's was unable to apply query personalizations due
    /// to conflicts with the form's query.
    /// </summary>
    /// <param name = "_sourceQuery">Query object with saved view query personalizations</param>
    /// <param name = "_targetQuery">Query object to be executed</param>
    /// <returns>Method has performed any modifications to the form's query</returns>
    [Replaceable]
    public boolean OnFailureQueryPersonalizationApply(Query _sourceQuery, Query _targetQuery)
    {
        boolean                 ret = true;
        int                     filterCount,
                                i;
        QueryBuildDataSource    qbdsTarget;
        Map                     skipRangesDS    = new Map(Types::Integer, Types::Class);
        Map                     skipRangesFields= new Map(Types::Integer, Types::Integer);
        QueryFilter             queryFilterSource,
                                queryFilterTarget;
        FieldId                 fieldId;
        TableId                 tableId;

        // define fields, which should be skipped
        skipRangesFields.insert(fieldNum(SalesTable, SalesStatus), 1);
        skipRangesFields.insert(fieldNum(SalesTable, InterCompanyOrder), 1);

        // add each Map to it's own data source
        skipRangesDS.insert(tableNum(SalesTable), skipRangesFields);

        filterCount = _sourceQuery.queryFilterCount();
        for (i = 1; i <= filterCount; i++)
        {
            queryFilterSource   = _sourceQuery.queryFilter(i);
            tableId             = queryFilterSource.dataSource().table();
            if (skipRangesDS.exists(tableId))
            {
                skipRangesFields = skipRangesDS.lookup(tableId);
            }
            else
            {
                skipRangesFields = null;
            }
            fieldId     = fieldName2Id(tableId, queryFilterSource.field());
            if (skipRangesFields && skipRangesFields.exists(fieldId))
            {
                continue;
            }
            qbdsTarget = _targetQuery.dataSourceTable(tableId);
            if (qbdsTarget)
            {
                queryFilterTarget = _targetQuery.addQueryFilter(qbdsTarget, queryFilterSource.field());
                queryFilterTarget.value(queryFilterSource.value());
            }
        }

        return ret;
    }

We were unable to apply the filters associated with this view due to security restrictions on this page. However, personalizations for this view have been applied.

Links:

https://learn.microsoft.com/en-us/dynamics365/release-plan/2023wave1/finance-operations/finance-operations-crossapp-capabilities/new-extension-methods-improved-handling-default-queries-saved-views