New UX - field does not show period

Options
bbolton
bbolton Member, ALL USERS, Partner Posts: 5 Occasional Contributor
in User Experience

Hi:

 

I have a module where I can enter end period for my business case that uses a customized time range (not model calendar)

bbolton_1-1588852026013.png

However, when I want to fill in the data in the New UX, the values that lies outside of the model calendar are not visible.

 

For example. When I select Project April:

bbolton_2-1588852123840.png

As you can see, the end date is not visible (however) the model indicates that Mar 2025 have been chosen and all calculations work.

 

Another example, Project Winter:

bbolton_3-1588852214417.png

 

The end period is within the model calendar, hence visible.

 

Is there anyway to change so the "Fields" card in the New UX visualizes periods beyond model calendar?

 

Br

 

Bjorn

Tagged:

Comments

  • bbolton
    bbolton Member, ALL USERS, Partner Posts: 5 Occasional Contributor

    Hi,

     

    Hmmm, so it works for you?

     

    I am wondering if it needs to be escalated to support for my specific model or if it's a general issue

  • benjamin_audroi
    benjamin_audroi Member, ALL USERS, GroupMember, Partner, Certified Model Builder, Community Pioneer Posts: 5 Master Anaplanner of the Year

    Hi Bjorn, 

     

    I don't if you followed through on this but I've had the same problem several times. 

     

    It seems this happens everytime you select a time period that is outside of the model calendar but is inside one of your time ranges. In the classic UI everythings works fine but in the New UX, it displays just "Find...". It does not have any impact on calculations, it is just a display problem. 

     

    br,

     

    benjamin 

  • benjamin_audroi
    benjamin_audroi Member, ALL USERS, GroupMember, Partner, Certified Model Builder, Community Pioneer Posts: 5 Master Anaplanner of the Year

    Hi @filip.sypniewski ,

     

    It happens on field cards when using a time range outside the model calendar range.

     

    I contacted the Anaplan support on this topic back in october last year. I was told it was indeed identified as a bug by the Product Team and that it was planned to be fixed in a future release. It has not been fixed as of today though.

     

    The only solution i can think of is to extend to model calendar range so that it contains the year FY23 and FY24, but you may not want to do this for other reasons. However, even though it displays "Find...", the value stored is still the right one, so it does not impact your calculation, only what you see on the field card.

     

    Hope that helps

     

     

Categories