The following map rules all output the value of A:
Using the same input data, these map rules always output the value of FMap(B):
I'm drawing a blank on this. How do I output the value of A when present and the output of FMap(B) when it is not?
Thanks, Jim Divoky
This topic has been locked.
4 replies Latest Post - 2012-11-19T18:36:37Z by SystemAdmin
Pinned topic Issue with map rule executing EITHER(A, FMap(B))
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-19T18:36:37Z at 2012-11-19T18:36:37Z by SystemAdmin
Re: Issue with map rule executing EITHER(A, FMap(B))2012-11-16T22:18:04Z in response to SystemAdminI've simplified my map rules and my results still make no sense.
=Date - The map rule returns the date value 20120902, 20120903, etc., as the parent FMap loops.
If I change the map rule to:
=EITHER(Date, TEXTTODATE("20121116")) - The map rule returns 20121116 on every loop.
Re: Issue with map rule executing EITHER(A, FMap(B))2012-11-19T18:36:37Z in response to SystemAdmin>> Could this be a "data binding" issue?
Thanks for the suggestion. That's what I thought initially so I passed a second copy of the input without good results. Then I simplified the map rule in the functional map and still had an issue.
In the input, the value of Date is present 5 times and missing 5 times. The following occurs with each of these map rules:
= Date Date is present 5 times in the output and missing 5 times.
= EITHER(Date, NONE) Date is present 5 times in the output and missing 5 times.
= EITHER(Date, TEXTTODATE("20121116")) All ten Date fields contain 20121116.
Now I've eliminated the EITHER function and am using a LOOKUP function. It appears to be working as expected. I still have to add three more conditions to the map rule though. I hate ACORD data!