Inventory Posting Setup

iansilvers

I am experiencing a strange problem in NAV2013 R2 when trying to enter new Inventory Posting Setup records. I am unable to enter a location code when trying to add a new record. I can lookup on the Location Code, but the value is not being populated. I ahv checked and there is no code behind the Location Code on either the table or page. I can run the table from the development environment, and can enter records that way, but from the RTC, I am struggling to create new records.

I have tried in standard CRONUS, as well as customer database, all without any joy.
The table and page are the same versions as in NAV2013, and they work as expected.

Has anyone else encountered this, and how did you get around it?

mohana_cse06

Check whether the page is opened in View mode or Edit mode

lohndorf

Hi Ian,

I guess you are on a build between 35727..35796. There was a problem temporarily like this if you have also un-editable fields on the page as you do near the bottom of Inventory Posting Setup. So a quick-fix could be to remove those fields on the bottom of the page. Or get hold of newest build. It should work again from build 35915 (KB 2907589),


/Lars

Tharanga_Chandrasekara

As Mohana said please check the page. If it is in view mode you cannot modify any records. First you need to click edit.
Plus does NAV show any error or any related message when you try to select the Location Code?

gravecz

It's not problem in view/edit page property guys. Lets try it on your own.

I have latest build 35800 and this bug is still there. You simply can't create new inventory posting setup combination.

There is one way how you can solve this: Use RapidStart services. Create new configuration package (with T5813) and fill this combination to EXCEL and then apply package. It ll create you what you want and then you can fill ACCOUNTS directly in page Inventory posting setup..

There is no other way up to build 35800 !!

iansilvers

Turns out it was a problem with Update Rollup 2, which has been corrected in Update Rollup 3. I am now on build 36035, and it works again.