Ir al contenido
Se marcó esta pregunta
12 Respuestas
63690 Vistas
Avatar
Juan Formoso Vasco

I added a function to a model, to set the default value of a field:

_defaults = {
    'template_id': _my_function,
}

In that function, I check some conditions and return the value. In one of those conditions, I have to show a warning message before returning the value. How to do this without stopping the normal execution of the program?

For example, the option warning does this:

'warning': {
    'title': _('Warning'),
    'message': _('My warning message.')
}

But it must be used in a return, and in this case, because of the function is called from defaults, it can't return a dictionary with a warning, but the value of the template_id.

The orm/osv exceptions make the following window a blank popup, I only want to notify some aspect to the user and then leave them working as if nothing had happened. In summary, how to show a simple info message?

Does anyone know it, please? 

Avatar
Descartar
Ludo - 21South

By default this would not be possible. I have thought about the same thing before, so I will watch this issue closely for a fix of some sort.

Ludo - 21South

By the way: A very dirty hack would be fire up a wizard which can have a cancel button as well as a regular "ok" button to continue with the flow.

Juan Formoso Vasco
Autor

Thank you Ludo! If I tried to do the hack you tell me, how can I fire up a wizard inside a function which is called from _defaults? I mean, the only way I know to fire up a wizard in python is through the return, so if I do that, it will generate an error because I'm not returning a right default value for the field, but a form.

Ivan

Juan, the problem is that when _defaults is called, it does not have to be from the UI. It can be from a cron job, etc. So, in a way, there is no guarantee you have a UI when _defaults is called. Is there any way that you can default the value of the field from another way that is guaranteed have UI? One example is the on_change which already has the warning mechanism.

Juan Formoso Vasco
Autor

The field I am trying to load its default value is a selection field. Do you mean this? Adding a new variable to the context in the function called from _defaults, and modifying its onchange method to show there the warning depending on the new variable added to the context?

Ivan

Juan, what I mean is that _defaults can be called even if it is not triggered from a UI component. _defaults will be called if the copy_data() or create() method is called. So, if you have a cron job or workflow that creates that model, it will call _defaults. In those situation the warning cannot be prompted. So, I think you need to find another way to defaulting the value of the field this if you insist on prompting the warning. I'm not sure what will work until you can describe how you're going to use template_id field and what conditions are you checking.

Ludo - 21South

John Doe is absolutely right here. The defaults can be called from everywhere in the code. If you want something specifically for the GUI, consider using on_change methods on your fields to give the desired effects.

Juan Formoso Vasco
Autor

Ok. Thank you both of you!

Avatar
Lucio
Mejor respuesta

I would recommend doing an onchange function on the field template_id and check the value returned there. 
The function for the onchange will be called for the default value and there you will be able to return the desired warning message.

I do not know if you are working on V7 or V8, for simplicity i will state the solution for v8 you can just do something like:

@api.onchange('template_id')
@api.multi
def onchange_template_id(self):
    res = {}
    if <do your checks here>:
        res = {'warning': {
            'title': _('Warning'),
            'message': _('My warning message.')
        }
    if res:
        return res

Hope this helps!

 

Avatar
Descartar
Juan Formoso Vasco
Autor

Hi! I'm working on v7. I'm going to try this right now, and I'll comment you the result. Thank you!

Juan Formoso Vasco
Autor

That's great Lucio! However, if I update the context in _my_function (called from _defaults) to add a variable to check in onchange, it doesn't appear here, and I can't check if I have to show the warning or not. I need to pass that variable from _defaults to the onchange.

Nimesh Jadav

That's not working in the mine, V13

Dimas Aditya Kristianto

this is working on V16

Avatar
Cristhian Carreno
Mejor respuesta 
Test ODOO 12

@api.onchange('field')
def my_function(self):

	#### CODE

	#### ASSIGN VALUE

        return {
            'value': {'other_id': arr_est},
            'warning': {'title': "Warning", 'message': "What is this?"},
        }

    #### OR APPLY DOMAIN

 		return {
		    'domain': {'other_id': [('partner_id', '=', partner_id)]},
		    'warning': {'title': "Warning", 'message': "What is this?"},
		}
Avatar
Descartar
M M Shahriar Amin

how can I make the text color red ??