Contributors mailing list archives
Re: Issue with allowed_user_ids ?by Alexey Pelykh <firstname.lastname@example.org> - 31/08/2019 15:12:03
With the help from community, it was found. It’s from project_hr module, it alters declaration on user_id field. And Pedro Baeza needs to take a look at that part of project_hr module as it’s his. I think that part should be changed a bit to introduce constraint on user_id field and alter domain in XML, not in code.
On Aug 31, 2019, at 14:57, Lorenzo Battistini <email@example.com> wrote:Do you know where allowed_user_ids is defined and used?On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <firstname.lastname@example.org> wrote:Dear community,Sorry for bothering via email, but I’ve encountered a very odd issue that goes beyond my area of knowledge. Please see https://github.com/OCA/project/pull/570It fails on OCA Travis, but works on our Travis, and fails with oddest issue ever:
Field 'allowed_user_ids' used in attributes must be present in view but is missing: - 'allowed_user_ids' in domain="[('id', 'in', allowed_user_ids)]"I’ve tried:
<field name="allowed_user_ids" invisible="1"/>adding this fixed OCA Travis, but breaks Runbot and our Travis. Not having that line (which seems really correct to me) is perfectly fine for Runbot and our Travis, but breaks OCA Travis. Any ideas?Alexey