nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

propagating catalog variable to BOM

medini_1036016653

As described (again) in detail to Nino Gabriel, we need to define a part type's prediction variable voltage "U" as "derived" in the element library, so that the actual voltage U can be set for the part (instance of the part type) in the BOM. Unfortunately this leads to spamming the project's warnings:

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023641097

Hallo Peter, ich hab das bei uns in den Feature Request Prozess eingepflegt. Die Lösung wird wahrscheinlich drauf hinauslaufen, die Variablen auch am Package bzw. HW Lib angeben zu können. Viele Grüße Nino

All comments

medini_1024120963

Hi Peter, thank you for bringing up all the issues you face in terms of usability and your ideas about how to solve them. In this case we have a latent behavior thanks to the customization you did. A warning does not always mean that you are supposed to act. It can be treated as a strong hint. In your case you may run into the threshold of warnings due to this. Therefore you can also enlarge the number of warnings in the medini preferences to ensure you receive all of them. Best regards Joël

medini_1036016653

Daer Joel, increasing the limit (9999 is the maximum permitted value) does not seem to change the behavior: Is there a way to make the BOM aware of a replacement value for a variable, when the checkbox "derived" is checked? I couldn't find a way, but who knows.. Best regards Peter

medini_1023641097

medini_1036016653

Hallo Nino, danke. Passt für mich :-) Schöne Grüße Peter

medini_1036016653

Is there an update available? Being confronted with >10.000 warnings keeps to be slightly annoying.

medini_1023641097

Hello Peter, sorry to hear that this point still causes frustration. Unfortunately I can not update you on our development status. Even in the Release Notes this would not be a named feature but rather one of the infamous "many more enhancements". Best regards Nino

medini_1036016653

Hi Nino and Krasimira, can I take from your message that this issue is not even adressed towards the development team? Have a year ago you had stated my inquiry entered "the feature request process". While this is of lower priority, these warnings have in the past months been source of confusion to new medini users at ZF. Typically this confusion has to be lifted by me giving a lengthy explanation. Thus I would appreciate for that to be resolved. Best regards Peter

medini_1024120963

Hello Peter, thank you for asking for clarification on the matter. I understand that this issue is it is important to you. I can assure you that the enhancement proposal was filled in the proper channels already. We are classifying it as non-blocking and hence treat other enhancement proposals you have raised with higher priority. Please consider that time is needed to evaluate enhancement proposals in our planning and quality management processes and that the implementation and scheduling is subject to discussion in those processes. We will reach out to you and let you know when it is available. BR Joël

medini_1036016653

Hi Joël, thank you for clarifying. Best regards, Peter