Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
1275 Widoki

Hi,


I have a custom computed field that I use in v17. This is calculating the latest date among a list of dates


When I upgraded to v18 on a test database, I get the following error

ValueError: Cannot convert mycustommodel.mycustomfield to SQL because it is not stored

If I change the parameter of my field  to "stored", then I no longer have the error but the field isn't computed anymore. Empty.


Here is the Python code for the computation :

for record in self:

    dates = []

    for line in record.custommodelwheremydatesare:

        if line.fieldwithdate:

            dates.append(line.fieldwithdate)

    if dates:

        record['mycustomcomputedfield'] = max(dates)

    else:

        record['mycustomcomputedfield'] = False


Any idea ?

Awatar
Odrzuć
Autor Najlepsza odpowiedź

OK I understood. The problem was because my list view was sorted according this computed field.

It didn't work but I left it that way.

When you migrate to v18, what was a mere useless option ended up crashing the interface.

Takeaway : do not sort your list using a computed field

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
1
kwi 24
2470
4
sty 24
1798
1
maj 21
4429
1
lip 25
602
1
gru 24
1924