Hello,
I used MashZone 2.0.0.2.1116 for over one month, it worked very well without any mistakes (most problems occured due to my lack of experience with the program).
Anyway, yesterday I've decided to upgrade to the new MashZone 2.1 version. First I exported all my MashApps and DataFeeds. Then I installed the upgrade and imported my MashApps and DataFeeds again.
Surprisingly, I can't use some filter elements any more. The calender still works, but my my user input box which acts as a day filter does not work anymore. I've checked the dependencies, but everything is correct.
Additionally, the filter elements in the Demo process MashApp also do not work. :-O
I don't know if that's a common bug in MashZone 2.1, or if it just happened to me.
After my downgrade to 2.0.0.2.1116, everything works perfect again. Do you have any idea what went wrong here?
Any tips are appeciated :)
Dear Jürgen,
I gave the update process a second try, but it still does not work, and I think I could figure out why:
The original date column (PSTDAT) has this format:
yyyy-mm-ddT00:00:00
That's the reason why I use the round up/down date element to cut off the time tag.
I'm pretty sure that this PSTDAT format causes the error. But the calender also uses this format, and it works. Just the input form does not work with it.
The normal calender uses the PSTDAT and works fine, the user input form uses the rounded PST_Day and does not work. But it works with the old 2.0.0.2 version. Strange.
AGAIN: The old MashZone version (2.0.0.2) works just fine with the solution shown above, both for the calender and the user input form.
Can you think of any workaround or should I go back again to the older version?
Update:
In the meantime, I played with several potential solutions to my problem and I could solve it:
I select the first 10 parts of the date field and then change the data format.
To sum it up, I would not define my problem a bug in the new MashZone 2.1 version. But it is still strange why the new version treats the existing date field in a different way than the older version, istn't it? :-P
Dear Markus,
we have checked your scenario and we can confirm that this is indeed a MashZone bug. Under certain circumstances, a date - which has the same value (expressed or viewed as text) than another value is different 'internally' (in your example from the calendar control). That's why the filtering / comparison fails.
You already did the right steps to work around the problem.
The general workaround is to convert the date column to the type 'text' and back to date. This assures, that the all feed calculations on the date values work correctly.
We will fix this bug with the Hotfix resp. next minor release of MashZone.
Kind regards
Jürgen Kirsch
