Page 2 of 2

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Sat Dec 02, 2017 12:25 am
by vineet
Thanks. RegBusinessObject seemed limiting to me as we cannot create relations.

If anyone else is stuck on the nullable issue, I handled it by doing the null checking like this:

StiNullValuesHelper.IsNull(this,"ClassName.PropertyName") ? "Null" : "Not null"

The expression editor sometimes throws that StiNullValuesHelper is not recognised in the context but you can safely ignore that warning.

Cheers

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Sat Dec 02, 2017 9:27 am
by Edward
Hi Vineet,
vineet wrote: If anyone else is stuck on the nullable issue, I handled it by doing the null checking like this:
StiNullValuesHelper.IsNull(this,"ClassName.PropertyName") ? "Null" : "Not null"
The expression editor sometimes throws that StiNullValuesHelper is not recognised in the context but you can safely ignore that warning.
Thank you for this very useful information. Do you mind to send the example of this problem recreated or any steps to recreate the problem here or to support[at]stimulsoft.com, so we could fix the issue?

Thank you,
Edward

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Sat Dec 02, 2017 11:42 pm
by vineet
Hi Edward,

Here's the expression editor when I open up any text label.

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Mon Dec 04, 2017 9:48 pm
by Alex K.
Hello,

We have added this task to our to-do list.
We will try to fix it fast as possible.

Thank you.

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Wed Dec 06, 2017 1:37 am
by vineet
Appreciated. Thanks.

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Fri Dec 08, 2017 9:16 am
by Alex K.
Hello

We are always glad to help you!
Please let us know if you need any additional help.

Thank you.

Re: DateTime column: why dictionary type is not "datetime (n

Posted: Sat Dec 16, 2017 6:54 am
by Alex K.
Hello,

The issue is fixed. The fix will be available in the next build.

Thank you.