Skip to content

[17.0][MIG] logistics_planning_base: Migration to 17.0#207

Closed
ChristianSantamaria wants to merge 22 commits into17.0from
17.0-mig-logistics_planning_base
Closed

[17.0][MIG] logistics_planning_base: Migration to 17.0#207
ChristianSantamaria wants to merge 22 commits into17.0from
17.0-mig-logistics_planning_base

Conversation

@ChristianSantamaria
Copy link
Copy Markdown
Contributor

Standard migration to v17

dalonsod and others added 22 commits January 27, 2026 09:33
Base addon for logistics management
…ptional all fields in tree view and modify some translations
With this improvement, new tools for massive schedules mark as finished
are added.

And, when logistics_planning_mgmt_weight is installed,
schedule inputs are not automatically marked as finished when a ticket
(move) is selected, so massive marking schedules as finished becomes
important.
…hods

Some onchange methods had write() calls within, that could lead to
unexpected results. In that cases we should use dot (".") notation or
update() calls.
With this improvement, it's possible to duplicate those logistics
plannings manually created. Some of the fields were reset anyway (like
state, linked stock move, invoicing, etc). Parametrized multi
duplication is allowed (selecting a certain number of schedules to be
duplicated, with a custom limit that prevent a user error selecting
"Duplicate" action when it wasn't intended to).
…dules

This is allowed for manual schedules at 'ready' state. An extra code
that prevents saving a schedule with move but without partner is added.
…nly users

If a user that have read-only access to logistics schedules loads any
view that computes partner_readonly technical field, an error is raised.

Addon logistics_planning_mgmt_weight adds a menu for this limited access
users, so an error is raised. This fixes it.
…o schedules

Co-Authored-By: David Alonso <david.alonso@solvos.es>
@dalonsod
Copy link
Copy Markdown
Contributor

Replaced by solvosci/slv-logistics#1

@dalonsod dalonsod closed this Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants