Navision 4 SP1 Bugs

Jonathan2708

Hi,

This week I have upgraded a customer from 4.0 to 4.0SP1, and my biggest disappointment is that the problem with the navigation pane where it stretches and takes up the entire screen meaning the other forms cannot be seen has still not been fixed. Does anybody know if there is a hotfix planned for this? My end users are getting rather fed up of re-configuring up all their favourite column settings every time we delete a zup file.

While on the subject of SP1, some new bugs I have found (not mentioned in the SP1 Known Issues document) :

1. Table 32 - Item Ledger Entry, missing a required key
2. Table 5802 - Value Entry, missing a required key (prevents Stock Not Invoiced reports from running)
3. Table 296 - Reminder Line, missing some SumIndexFields (prevents create reminders function from working)
4. CodeUnit 392 - Reminder-Make, variable defined as Code[10] when should be Code[20] (prevents create reminders/suggest reminder lines from working)

Luc_VanDyck

Jonathan2708 wrote:

Hi,

This week I have upgraded a customer from 4.0 to 4.0SP1, and my biggest disappointment is that the problem with the navigation pane where it stretches and takes up the entire screen meaning the other forms cannot be seen has still not been fixed. Does anybody know if there is a hotfix planned for this? My end users are getting rather fed up of re-configuring up all their favourite column settings every time we delete a zup file.

[...]

Try this download: Fix Navision Zup-File v1.0

kriki

Check Fix Navision Zup-File v1.0
For the missing keys: probably they exists, but they aren't enabled. You just have to enable them.

DarkSide

I appear to be having problems with transfers of lot controlled inventory in SP1. The "receipt" or "inbound" side of the transfer no longer has the lot information from the shipment side. Better yet, you cannot enter it (field is uneditable). So, I have to insert reservation entries by hand. It's really fun...

Anyone else experience this?

kine

Some keys was changed on the tables (optimized). Check your reports if they are using same keys as original reports (if there are customized)

Jonathan2708

Just to say all the bugs I reported above were produced using the standard off the CD installed objects (GB version).

Jonathan