Hi Eric

Nice to hear from you again!

Please confirm the following:

1. Evolution version and build?

2. Report Manager version?

3. Are you running the standard BIC Inventory Master report layout in which NO (nothing / nada) customizations in MS Excel or in the report container have been made?
4. If you create a brand new company, capture a few dummy stock items and process a few dummy GRV/invoice transactions, and then run teh report, are you able to recreate the error?

5. Please include a screenshot of the error.

6. Have you allowed Bins per Warehouse in the companies where you observe the error? Or is this not even a factor for the error to be displayed?

Kind Regards

Bennie

Hi Eric

Nice to hear from you again!

Please confirm the following:

1. Evolution version and build?

2. Report Manager version?

3. Are you running the standard BIC Inventory Master report layout in which NO (nothing / nada) customizations in MS Excel or in the report container have been made?
4. If you create a brand new company, capture a few dummy stock items and process a few dummy GRV/invoice transactions, and then run teh report, are you able to recreate the error?

5. Please include a screenshot of the error.

6. Have you allowed Bins per Warehouse in the companies where you observe the error? Or is this not even a factor for the error to be displayed?

Kind Regards

Bennie

Hi Bennie

i think the issue report version from what I’ve read up, it’s Inventory Master 4-2 and think needs to be updated to 4-7. Where can I get that?

Hi Eric

Sorry, can you please also answer the questions above so I can first form a complete picture of this query?

Hi

Please see answers as required.

1. Sage Evolution 10.1.3.007

2. Report Manager Core 7.50.0, Metabase 6.9.4

3. Yes

4.Can't do as don't have access to do so. They have just moved to EvolutionAnywhere

5. 

6.Yes

Also note, If I remove Bin then get error Qty_On_Hand column invalid, and as I delete new columns appear as invalid.

Hi Eric

Thanks for the feedback 

Ok, your query deserve to be treated in a more formal way as I haven't seen this one before.

Therefore, please log your query with Sage Evolution Support in the usual way but request that the new support ticket be sent for my attention and I will then continue on this matter.

Of course, please include as much details as possible and the screenshot of the error.

Blessings!

Bennie