Curious “currency accounting” field behaviour (bug?)

Tap Forms Database Pro for Mac, iPhone, iPad and Apple Watch Forums Using Tap Forms 5 Curious “currency accounting” field behaviour (bug?)

Tagged: 

Viewing 1 reply thread
  • Author
    Posts
  • October 20, 2020 at 7:19 AM #42323

    Ben Carter
    Participant

    Hi,

    I’m a new user of Tap Forms and really liking it thus far – it strikes an exceptionally good balance between usability and features IMHO.

    I have run into a weird behaviour with one of my layouts, though, that I’m not sure if it’s my fault or a bug.

    Basically, I have four currency-formatted fields containing values in GBP, EUR, USD and JPY. They’re each set as “currency accounting” format with the appropriate currency and number of decimal places, and show up as such (“US$1.00”, etc).
    If I’m in the default layout, I can edit any of them and it works correctly – for example, if I edit the “US$1.00” entry, delete the final “0” and replace it with a “5”, I get “US$1.05” and that saves correctly when I leave the field.

    However, I have a custom layout with those four fields placed on it, and in that case the only field I can update this way is the GBP field – if I edit any of the other three that way, as soon as I move off the field it reverts to its previous value. However, if I delete the currency prefix (in other words, editing “USD$1.00” to “1.05” instead of “USD$1.05”) then the value change is saved correctly.

    At a very rough guess, it looks a lot like for some reason the code for those fields in custom layouts doesn’t parse the currency prefix properly and thus rejects the change as being a malformed value? Although I have no idea why the GBP field works if that was the case (at first I thought it might be because it’s just got a single-character prefix, but EUR is the same…)

    This isn’t a critical problem for me, but it’s somewhat odd and so I thought I’d report it in case it was a bug, or there was something I’d done to cause it somehow.

    October 22, 2020 at 12:10 AM #42353

    Brendan
    Keymaster

    Hi Ben,

    Thanks for the bug report! And sorry for my delayed response.

    I’ll investigate this issue.

    Brendan

Viewing 1 reply thread

You must be logged in to reply to this topic.