Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Null values in MIF

From: C (2013-03-07 14:02)

I must be missing something incredibly simple here.
It's great that we can now use "~NULL~" to overwrite fields that have a value with NULL through the MIF.
The problem is when the field is less than 6 characters long. First, you can't put ~NULL~ in the interface table if the field is too short. Then, when I expanded the field in the interface table and tried to run it in, it went to Message Reprocessing as "Value exceeds maximum length".
I'm feeling particularly dense. What am I missing?
Thanks


From: dennis_belandres (2013-03-07 09:13)

I may be over simplifying things here, but can't you just leave the value
blank or white space in the incoming file?

Regards,

Dennis B





"C" <corpuscle2@yahoo.com>
Sent by: MAXIMO@yahoogroups.com
03/07/2013 09:02 AM
Please respond to
MAXIMO@yahoogroups.com


To
MAXIMO@yahoogroups.com
cc

Subject
[MAXIMO List] Null values in MIF







I must be missing something incredibly simple here.

It's great that we can now use "~NULL~" to overwrite fields that have a
value with NULL through the MIF.

The problem is when the field is less than 6 characters long. First, you
can't put ~NULL~ in the interface table if the field is too short. Then,
when I expanded the field in the interface table and tried to run it in,
it went to Message Reprocessing as "Value exceeds maximum length".

I'm feeling particularly dense. What am I missing?

Thanks











The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.


From: C (2013-03-07 14:18)

Thanks for the reply.
If you have a null value in the interface table, Maximo assumes that you don't want to overwrite the destination value, so it won't replace the value with a null. It's a valid assumption more often than not.
--- In MAXIMO@yahoogroups.com, dennis_belandres@... wrote:
>
> I may be over simplifying things here, but can't you just leave the value
> blank or white space in the incoming file?
>
> Regards,
>
> Dennis B
>
>
>
>
>
> "C" <corpuscle2@...>
> Sent by: MAXIMO@yahoogroups.com
> 03/07/2013 09:02 AM
> Please respond to
> MAXIMO@yahoogroups.com
>
>
> To
> MAXIMO@yahoogroups.com
> cc
>
> Subject
> [MAXIMO List] Null values in MIF
>
>
>
>
>
>
>
> I must be missing something incredibly simple here.
>
> It's great that we can now use "~NULL~" to overwrite fields that have a
> value with NULL through the MIF.
>
> The problem is when the field is less than 6 characters long. First, you
> can't put ~NULL~ in the interface table if the field is too short. Then,
> when I expanded the field in the interface table and tried to run it in,
> it went to Message Reprocessing as "Value exceeds maximum length".
>
> I'm feeling particularly dense. What am I missing?
>
> Thanks
>
>
>
>
>
>
>
>
>
>
>
> The information contained in and transmitted with this Email may be
> privileged, proprietary, confidential and protected from disclosure. No
> privilege is hereby intended to be waived. This Email is intended only for
> the person to whom it is addressed. If you are not the intended
> recipient/addressee, any use of the Email and/or its contents, including,
> but not limited to, dissemination, distribution or copying is strictly
> prohibited and may be unlawful, and you must not take any action in
> reliance on it. If you receive this Email in error, please immediately
> notify the sender and delete the original message and any copies of it
> from your computer system. We deny any liability for damages resulting
> from the use of this Email by the unintended recipient, including the
> recipient in error.
>
>
>
>
>