Skip to main content

Persist filter and keep filter expanded

Many of you have problably seen these blog posts

Persisting Filter conditions in EP Grid
http://blogs.msdn.com/b/epblog/archive/2009/08/29/persisting-filter-conditions-in-ep-grid.aspx

and

Always keep the Filter section expanded in AxGridView
http://community.dynamics.com/product/ax/axtechnical/b/axsolutionsmonkey/archive/2009/04/02/always-keep-the-filter-section-expanded-in-axgridview.aspx

They are excelent to use togather i.e. persist the filter and keep the filter open as well

I implemented two static methods in the EP class to persist the filter, then i can use oneliners to persist the filter of any dataset.

Also have in mind that if the PersistState of the ASP.NET dataset is set to false the filter is not persisted. So check out that the property is set to true, it is true by default







public static void packDataSet(Name _name, container _value, QueryRun _queryRun)
{
    SysLastValue    sysLastValue;
    ;
    ttsbegin;
    // Delete last saved query for the current dataset

    delete_from sysLastValue
        where sysLastValue.Company      == curext()
           && sysLastValue.UserId       == curuserid()
           && sysLastValue.RecordType   == UtilElementType::DataSet
           && sysLastValue.elementName  == _name
           && sysLastValue.DesignName   == _name;
    // If there is a new queryRun() object then serialize and save it
    // in the sys last value table
    // Put your datasource name

    if (_queryRun)
    {
        sysLastValue.RecId = 0;
        sysLastValue.Company        = curext();
        sysLastValue.UserId         = curuserid();
        sysLastValue.RecordType     = UtilElementType::DataSet;
        sysLastValue.ElementName    = _name;
        sysLastValue.DesignName     = _name;
        sysLastValue.value          =  _value;
        sysLastValue.insert();
    }
    ttscommit;
}


public static void unPackDataSet(Name _name, Query _query)
{
    SysLastValue    sysLastValue;
    Query           savedQuery;
    ;
    // get the last value from the sys last value table
    select firstonly sysLastValue
        where sysLastValue.Company      == curext()
           && sysLastValue.UserId       == curuserid()
           && sysLastValue.RecordType   == UtilElementType::DataSet
           && sysLastValue.ElementName  == _name
           && sysLastValue.DesignName   == _name;
    if (sysLastValue && sysLastValue.Value)
    {
        // If there is an unpack error delete the saved query

        if (!SysQuery::unpackRangeAndSortorder(_query, sysLastValue.value))
        {
            ttsbegin;
            delete_from sysLastValue
                where sysLastValue.Company      == curext()
                   && sysLastValue.UserId       == curuserid()
                   && sysLastValue.RecordType   == UtilElementType::DataSet
                   && sysLastValue.ElementName  == _name
                   && sysLastValue.DesignName   == _name;
           ttscommit;
        }
    }
}

Comments

Post a Comment

Popular posts from this blog

Dynamics 365 for operations – Table extensions

Background Extensions are a new way to add functionality and custom code to the D365 system without changing the standard code. In fact, Microsoft has announced that edit standard elements like those that we have done in the past will not be possible after 2017. By using extensions, we can achieve the same result by simply extending the standard system => EXTENSIONS. To read more about the difference between overlaying and extensions follow this link https://ax.help.dynamics.com/en/wiki/customization-overlayering-and-extensions/#extensions Extending tables By using table extensions, we can create a new table that adds new fields, field groups, indexes, mappings, relations, methods, subscribe to event handlers and more. When extending tables we need to follow the naming rule as such: <TABLENAME><_Extension> the compiler understands the _Extensions suffix and knows that the table in question is extending a table from the standard system. This gives us access ...
Post a Comment
Read more

Plug-able Authentication in Microsoft Dynamics AX 2012

I have worked in many projects involving the Enterprise Portal for Ax ranging from version 2.5. One of the biggest issue for the end customer/user has been the ability to have a plug-able authentication for EP. This has been an issue for example for customers that have other portals based on Share Point as well as custom build ASP.NET web sites. All these portals are able to share the authentication with Single Sign On, SSO. But until now with version 2012 of Ax this has not been possible since earlier versions of Ax have only supported Windows Authentication. So in scenarios where you implement an EP site for a customer that has other portals and uses for example forms authentication, if you are not running Ax 2012 you have to have a special/dedicated log-on to EP. One of the biggest advantages is the fact that now external users do not have to be in Active Directory mixed up with all the internal users or located in an extra AD repository with all the administrative IT work l...
Post a Comment
Read more

Remove HTML code from strings

When you work for example with the presentations DAX adds some HTML comment code to the text stored in the database. This can cause the text on the web to be displayed in incorrect format. This also takes up space in the database and makes the database file grow larger. <!--AXAPTA  MarginWidth="0" MarginHeight="0" WebletName="WebLet700062029" Type="WebPageWeblet" -->TEXT There is a nice X++ function: just call Web::stripHTML( string ), which will return the string without the HTML tags
Post a Comment
Read more