I have a bunch of Notrix jobs to migrate to LEI. In all cases I am transferrring or replicating data from SQL server to Notes. What stands out in my experience so far is that LEI is much more picky about data types than Notrix. For example, an existing Notrix job looks like this:
Note the type mismatch between the two LobComm fields. The field is Int in SQL Server but Text in Notes. Notrix seems to be OK with this but LEI won't allow it. My solution is to add another field to the Notes form, make it a Number field, and change the replication activity's field mapping to:
and then use data transformation to update the existing Text field that is used by the Notes selection formula, column forrmulas etc:
During insert:
Select @All;
FIELD LobComm := @Text(LobComm_Numeric)
During update:
Select @All;
FIELD LobComm := @Text(LobComm_Numeric)
That is all very simple. But the problem is the existing documents don't yet contain a LobComm_Numeric item, so when the job runs I get:
Connector A record key values: MainEntry = "retirement"; LobComm = 115
Connector B record key values: MainEntry = "pay cap"; lobcomm_numeric =
Of course I can run an agent on the data as part of the switch to LEI, but I don't want to. The ideal is that, apart from a few simple design additions to the Notes app, none of which is visible to the user, we simply switch the Notrix job off and switch the LEI job on.
So, two questions:
1. Is there a better way to overcome the type mismatch between SQL Server and Notes than the method I show above, that is, adding another field to the form?
2. Assuming No to question 1, is there a way to insert the necessary numeric item on-the-fly if it does not exist, as in Default LobComm_Numeric := @TextToNumber(LobComm)). I looked at doing that in the "Formula to execute during Select" field but that runs after the fetch; my problem occurs during the fetch.
Return to top
Question about datatype mismatches ... (Thomas Kennedy 7.Apr.04)
. . 
Print this page
