IC ERROR 11 - Journal is Not Supported, Dataport ERROR Help

boku25boku25 Member Posts: 39
edited 2004-11-11 in Navision Attain
Please Help,
I was creating a simple DataPort for General Journal Batch in Navision 3.60A. I imported a CSV file into Navision using some global variables, everything works fine(Everything Imports), but when I tryed to import text into the InterCompany field, I got that IC Error 11 - Journal is not supported in this version of InterCompany (InterCompany is a Text field).

What should I do? My boss is on me like cheese to Finish this simple Dataport. I tried everything?? There seems to be two tables connected to the field, Intercompany and Companies, but when I try to import a direct string (Ex: InterCompany := InterCo;) it should import. I tryed a SETRANGE, FIND, '-', COPYSTR, Global Variable: InterCo,

Can Anyone help.

Navision Newbee :shock:

Comments

  • ArhontisArhontis Member Posts: 667
    Hi,

    The table 232 Gen. Journal Batch in Nav GR 3.60 has the following fields:
      Journal Template Name Name Description Reason Code Bal. Account Type Bal. Account No. No. Series Code Posting No. Series Copy VAT Setup to Jnl. Lines Allow VAT Difference
    The InterCompany field isn't anywhere. Where did you find that?
  • boku25boku25 Member Posts: 39
    Well the company I work for is divided by many other companies. So the InterCompany is the general link to the main company that controls all companies. Its a Modification added to our version of Navision. Here's the problem everytime I try to import anything into that field InterCompany(InterCompany := InterCo; ) it gives me that IC Error, does not support Journal. If I lose the InterCompany, it runs perfectly.. can you help me, please..

    Thanks

    Boku25
  • ArhontisArhontis Member Posts: 667
    Hi Boku25,

    The error is very strange, maybe there is an internal function or variable that has the same name. It is like you make a field with the name COPYSTR and try to access it from code! Or perhaps the global var you use has a strange name. Try using another global var name.

    You could also try the assignment:
    "Gen. Journal Batch"."InterCompany":= ...
    
    (I added the quotes)

    The InterCompany field what type is it? does it have any relations to other tables? is it a part of a key?
  • boku25boku25 Member Posts: 39
    I am using table 81 Gen. Journal Line

    Thanks

    Newbee
    Boku25
  • ArhontisArhontis Member Posts: 667
    Hi,

    Have you tried the recommendations i mentioned?

    What about the InterCompany field? what type is it? is it a key? has relations?

    Try making a backup of your database, restore it to a test db, rename the InterCompany Field to something simple and meaningless and use the dataport again with the new name of the field. If the dataport works with the new field name then you will know that there is something wrong about the name of the field and plan a live rename of the field in your working database.
  • boku25boku25 Member Posts: 39
    InterCompany is TEXT 30
    Example: 050-OUTREACH HEALTH SVCS, INC.
    Within Intercompany field there's another filed called Companies that hold
    the same information example: 050-OUTREACH HEALTH SVCS, INC.

    So if you where typing in the intercompany name you would filter down to the companies table, that holds the same information.

    so that field is linked to the Intercompany and Companies table
    Text to Text

    Thanks
    Newbee

    Boku25
  • ArhontisArhontis Member Posts: 667
    If I understand you correctly:

    Companies field is a flow field with Lookup to the same table and the field InterCompany, and has Table Relation = "Gen. Journal Line".InterCompany

    InterCompany field has a Table Relation with Company.Name

    It seems a bit complicated...

    You could disable the relations in a test database and try each time the dataport and figure out what relation might cause the error.
  • boku25boku25 Member Posts: 39
    It worked!!

    I added a field in my test database called InterCompany2 ( I basically copied the Intercompany Field ) and added to the form and it import fine, so there something the relation inside the InterCompany Field, so its still a work in progess..

    At least I know where to start..

    Any ideas why this happens??

    Thanks very much...

    Boku25
  • ArhontisArhontis Member Posts: 667
    Hi,
    If you copied and pasted the InterCompany field, then the new field carries all the information the the original field have.

    Try to duplicate the other relations to your InterCompany2 field from other fields, like the Companies you have and import again.

    If you get the error, then its the Companies field relation that causes the error. If it imports again then the problem is the field name "InterCompany", so you have to rename it to "Inter Company Code" or something else to the original database.

    Could you be more specific about all the relations from/to the Intercompany field? Write all of them and with details so if you still have a problem, I could duplicate your solution here and debug the problem...
  • boku25boku25 Member Posts: 39
    In Table 81 Gen. Journal Line Table
    OLD Field 23001090 InterCompany TEXT
    NEW Field 57003 InterCompany TEXT

    I copied all the setting and renamed the old one InterCompany2 and the new became InterCompany, It now works perfectly, and both are identical, relation wise, the only difference I see id the number series there in, the old is 23001090 and the new 57003.. not sure if it matters

    Thanks
  • ArhontisArhontis Member Posts: 667
    Hi,

    I am glad it works... Tricky think though!
    Shouldn't you get rid of the old field now?
  • boku25boku25 Member Posts: 39
    I am trying to figure out what caused that error, I have my theories, we recently upgraded our navision and that might be the source.. Not sure

    I thank you very much,

    You are a true friend. :D

    Boku25
Sign In or Register to comment.