Field `profile_id` does not exist about wms HOT 5 CLOSED

Hi, I just installed the module in a new database without issue, and the profile_id field is defined here:

from wms.

Hi, I have no changes locally. I tried to install an earlier commit and it works fine. The problem might be that i started the database with no demo data. I'll investigate some more.

from wms.

Hi, I just installed the module in a new database without issue, and the profile_id field is defined here:

wms/shopfloor/models/shopfloor_menu.py

Lines 30 to 32 in 75411c8

	profile_id = fields.Many2one(
	"shopfloor.profile", string="Profile", help="Visible on this profile only"
	)

Are you sure you have no local changes in your wms repository?

I'm truly perplexed by this issue, changing the model (shopfloor.menu) property as below and in the corresponding model (shopfloor.profile) and in the view everything seems to work properly.

shopfloor_profile_id = fields.Many2one( comodel_name='shopfloor.profile', string='Profile', help='Visible on this profile only')

Could there be some kind of inheritance issue somewhere?

from wms.

@poiswe none of us has this issue (and we install this module many times for testing).
Do you still have problems?
If yes, please try w/ a fresh checkout of this repo and install it from scratch.

from wms.

Forgot to close this. In the end it was probably due to a mismatch between the shopfloor_base and shopfloor module or due to the fact that shopfloor_base was not installed. A lot of refactoring has been done since the issue and things seem to work real nice.

@simahawk I've started prototyping a reception-app in Ionic, are there plans to wrap the reception-screen logic as a rest-service?

from wms.