Salesforce

Data Mapper Troubleshooting (Magic xpi 4.7)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Data Mapper Troubleshooting (Magic xpi 4.7)

Q1

Why can't I save my project?

A1

Unsupported types can cause errors. If you have a problem with saving your project, and you are notified by an error message that the problem lies in a Data Mapper step, you should check that all of the types used in your project are correctly recognized by Magic xpi.

Click here for more information on saving projects.

Q2

How can I see SQL statements?

A2

If you are using databases, and you want to see the SQL statement that was sent to the database, you can use the DebugMapper=Y flag in the ifs.ini if you are running the project in the Server. Alternatively, you can activate the Data Mapper log through the IFS Settings interface.

Click here for more information about debugging the Data Mapper utility.

Q3

Why do I get an error when I define mapping connections?

A3

Certain Data Mapper connections between nodes of different types are not permitted, and the following error is returned:

Warning 124 – Mismatch in Data Mapper connection type

Here is a list of illegal connection types:

Alpha

>

Logical

Numeric

>

Date

Numeric

>

Time

Date

>

Numeric

Date

>

Time

Date

>

Logical

Time

>

Logical

Time

>

Numeric

Time

>

Date

Logical

>

Alpha

Logical

>

Date

Logical

>

Time

Q4

Why am I getting an "Invalid Statement" error?

A4

When you get to the end of a SQL statement and receive the Invalid Statement error, it means that you have tried using a Data Mapper utility to perform an INSERT into a table whose owner is not dbo and the connection to the database Destination is with a user that is not the owner of the table (sa instead of Magic xpi for Magic xpi's tables).This behavior is not allowed in Magic xpi.

Q5

What happens if I use numerics greater than 18 in Sources and Destinations?

A5

If a Source has a numeric picture larger than 18, a "Mismatch in Format" warning will be generated in the Data Mapper.

If a Destination has a numeric picture larger than 18, a warning will also be generated. To clear the warning, set a new picture of 18 or less, and check the Always Use Custom Picture box.

Q6

The Data Mapper window appears bigger than the visible screen. How do I fix this?

A6

Change your screen's resolution to: 1280 by 800 or 1280 by 1024.

Make sure the DPI setting is set to Normal size (96 DPI). To do this:

  1. Right-click on your desktop and select Properties. The Display Properties dialog box opens.

  2. Click the Settings tab.

  3. Click Advanced. The Default Monitor dialog box opens.

  4. Verify that the DPI Setting parameter is set to Normal size (96 DPI).

  5. Click OK to close these dialog boxes.

Q7

The Data Mapper converts negative numbers in a flat file to positive numbers. How do I stop this?

A7

To prevent this from happening, add the letter N to the number in the flat file's Format column.

Q8

Why do I get an "illegal variable" message on a valid expression in the Expression Editor?

A8

In the Data Mapper, when you add an expression to a Destination element, and the expression is based on a node from a Source and contains a reserved word, it is validated as true and the reserved word is changed to capital letters upon verification. Then, when you verify the expression again, it is invalid and the "illegal variable" message is displayed. For example:

Salesforce object Case: IF (Source/S4/CASE/row/Fields/Type ='a','b','c')

(When the Source is XML, the XSD is salesforce\XSD\Salesforce_1\Case.xsd, and the Destination is of any type.)

If you enter only the 'Source/S4/CASE/row/Fields/AccountId' Source node, it works correctly. However, if you use it within an expression, the problem occurs.

Therefore, when you click Verify, the expression is broken because there is a false positive when detecting reserved words. If you do not click Verify, and just click OK instead, the expression works correctly. If the expression has already been ruled invalid, you will need to rewrite the expression.

Q9

Why am I getting the "Unexpected character encountered while parsing value:" error when working with JSON in the Data Mapper?

A9

This error occurs if you select an invalid JSON schema file.

Q10

How come the flat file that I'm using in the Data Mapper is not getting created and I'm getting the "Destination directory does not exist" message?

A10

This can happen when using a mapped network drive. The Magic xpi service might not have sufficient privileges to create the file on the network drive. One possible solution is to make the mapping persistent. You do this by adding the map command in the magicxpi-setenv.bat file, so that the service can see the mapped drive in its session.

Q11

Why am I getting the "455: Source XML is not well formed" error?

A11

This error means that the XML is not well-formed, or that the XML itself may be well-formed but it does not match the expected XML.

Q12

Why am I getting the "Missing Format or Picture definition" error?

A12

If you have a field type in your schema that is not mapped to a default data type, such as an xs:union field type, you will get this error. To solve this issue, you need to define the field type in the Default Data Format repository.

During migration, if you had a field type that was mapped in the Mapper, but was not mapped to a default data type, after the migration process you will get a Checker error letting you know that you need to define your field type.

Note: The default data type can be set for a specific schema or for the entire project (depending on where the entry of the default data format is defined).

Reference
Attachment 
Attachment