Skip to Content

Contributors

Re: Issue with allowed_user_ids ?

Do you know where allowed_user_ids is defined and used?


On Fri, 30 Aug 2019 at 16:11, Alexey Pelykh <alexey.pelykh@gmail.com> 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/570
It 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

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--

by Lorenzo Battistini. - 02:56 - 31 Aug 2019

Reference

  • Issue with allowed_user_ids ?
    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/570
    It 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

    by Alexey Pelykh <alexey.pelykh@gmail.com> - 04:10 - 30 Aug 2019