NAV 2017 - Cronus DB Problem

Supremenerd88
Supremenerd88 Member Posts: 21
edited 2016-11-11 in NAV Three Tier
Hi all,

i've just install nav 2017 (italian) on my development server. i have a problem: in table 27 (Item) i have a field in SQL DB call "Has Sales Forecast" that i haven't in Development Evnironment.

Also, i have 5 tables thant i haven't in Development Evnironment:

[CRONUS Italia S_p_A_$Item Sales Forecast]
[CRONUS Italia S_p_A_$Item Sales Forecast Parameters]
[CRONUS Italia S_p_A_$MS - PayPal Standard Account]
[CRONUS Italia S_p_A_$MS - PayPal Standard Template]
[CRONUS Italia S_p_A_$Sales Inventory Forecast Setup]

What are this field/tables? Why Cronus DB has this objects in SQL and he hasn't in Development Evnironment? They are Italian objects or WW objects?

Thank you
Giorgio Gandolfi

Best Answer

Answers

  • chrisdf
    chrisdf Member Posts: 82
    Thanks for the reply.

    So to confirm ... are we saying that because my application was built on Cronus 2017 CU0 this will not work because I am trying to import Cronus 2017 CU1 and the CU1 release has some extensions loaded that were not there in CU0?

    So running an upgrade from CU0 to CU1 is OK from an object point of view but we now need to consider if MS are adding extensions to the new release?

    If so, is there an "idiots guide" as to what extensions are in the different releases and when doing an upgrade, how should we consider this in the "new world" i.e. should we all now think about upgrading objects and then adding in new extensions...
  • Jan_Veenendaal
    Jan_Veenendaal Member Posts: 206
    uhm, no. AFAIK these fields / tables should not be in CRONUS. They are not in CRONUS W1, I just checked.

    And, even IF they were there, IMHO it should not be an issue since it is perfectly possible to have more than 1 extension in the same environment.
    Jan Veenendaal

Categories