Hello
Using the month function you will get the month  Month(AddMonths(CustomerPurchaseOrder.POReceivedDate,-1))

You can apply the same for different results

Try this I hope this will help.

Thanks 

Hi,

You need to add the condition as per your requirement in the filter.

For e.g.

If(Dashboard_Filters.Filter_Month_Type_Id =Entities.MonthType.Last3Months,test.Months = Month(AddMonths(CustomerPurchaseOrder.POReceivedDate,-3)),

Hi Nihal,

Follow the correct statement for if conditions

if(condition,

if(Condition,true,false),

if(condition,true,false)

) 

you might getting syntax issue.

Regards,

Shoeb

There might be syntax error in your code as the filter mentioned in the question is correct.

Hi @Nihal Hegde ,

I doubt that you are applying the AddMonths to the correct date, and you are probably making this far more complex than it needs to be, and I find it astonishing it even is accepted by OS, as it doesn't even look like a correct expression evaluating to a boolean, and nowhere are you relating it to the date of today...

So you have Purchase Orders with a POReceivedDate.  And by choosing a filter option of X months, you only want to see orders with a ReceivedDate in the timeframe of X months before today, right ?

So your filter condition could be as simple as this :

Dashboard_Filters.Filter_Month_Type_Id  = NullIdentifier() 

or 

CustomerPurchaseOrder.POReceivedDate  >= AddMonths (CurrDate(),

If(Dashboard_Filters.Filter_Month_Type_Id=Entities.monthfilter.lastmonth, -1,

If(Dashboard_Filters.Filter_Month_Type_Id =Entities.monthfilter.last3months, -3, -6)))

....

Here's for a completely different approach :

If at all possible, I would try to pull any of this conditional hardcoded stuff out of my aggregate, to make it even simpler and more maintainable.

An example : you already have a static entity, just add an extra attribute of type integer with name months to that.  You probably have a dropdown to select this filter option, based on an aggregate retrieving the options from your static entity.  So, instead of storing the id of the choice, store the months value in a filter variable of type integer (let's call it MonthsToFilter).

Then, your filter becomes 

Dashboard_Filters. MonthsToFilter = 0 

or 

CustomerPurchaseOrder.POReceivedDate  >= AddMonths(CurrDate(), Dashboard_Filters. MonthsToFilter*-1)

If your users want other options to choose from in the future, it becomes a simple matter of changing your static, and the filter on the aggregate follows without any alterations.

....

And, you could take this even further, in the aggregate that feeds your dropdown of the static options, add a calculated attribute called "FromDate", with formula

DateTimeToDate(AddMonths(CurrDate(),MonthsToFilter*-1))

So now, you will need a filter variable of type date, and map the value of the calculated column of the dropdown to that.

Then your filter condition on your purchase order aggregate becomes even simpler

CustomerPurchaseOrder.POReceivedDate > Dashboard_Filters.FromDate

Dorine

Hi @Nihal Hegde,

I've attached the OML file for your reference. I was trying to implement the solution that @Dorine Boudry suggested, and I found that her last method seemed like it would be the most efficient. However, I wasn't able to get it to work on my end, so I ended up going with method two.

I wanted to take a moment to express my gratitude to @Dorine Boudry for her helpful explanation. All credit goes to her for pointing me in the right direction.

In case it's helpful, I found that method two worked well for me, and I was able to achieve the desired result.

Best regards,
Andrew_Smith