CaptionClass property not working for fixed layout in 2013

SambSamb Member Posts: 18
edited 2012-09-18 in NAV Three Tier
We have a form that uses a fixed layout so that the values can be displayed in a columnar view. In 2009 R2 this form works great. We wanted the field values to be displayed in the third column. To get the caption in the past we just put a "filler" text box in the first and second columns. The boxes in the first column then would get us the captionclass field to populate the text to display for the row caption. When we moved this page to the 2013 BETA the caption classes would not come in. I have tried re inputing the captionclass value and the entire field itself. Neither of these seemed to work. After this I tried to move the actual field into the first column, as the CaptionClass runs correctly if I run the table directly from the developer environment. This also did not bring in the caption. I was wondering if this issue had been reported or if there is something different that we have to do now for 2013?

Comments

  • kabrocokabroco Member Posts: 111
    Is the caption available in the language you work in? I found that pages are not htat flexible with ML as forms are, showing nothing when the ML was not present.
  • SambSamb Member Posts: 18
    I am using the ENU language in a NA database. The client does everything in the ENU. I am not grabbing a field caption rather the data defined in a particular field. I can use the same caption class in a factbox and I get the correct value to display. The only page that does't seem to work for me is one with a fixed layout involved.
  • Tommy_SchouTommy_Schou Member Posts: 117
    Can't help you but only relate a similar experience.

    Creating a test page with 2 labels. One where CaptionML is used to determine the caption (DAN=Beløb;ENU=Amount) and another where you use a text-constant that you put into the CaptionClass property (Again with text-constant set to DAN=Beløb;ENU=Amount) will give a kind of funny result.

    The field where CaptionML is used is correct when using DAN language. The other field shows the ever so famous (in Denmark at least) ¢-sign instead.

    Like so:
    Best regards
    Tommy
  • SambSamb Member Posts: 18
    Just following up, to see if anyone found an anwser yet?
Sign In or Register to comment.