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; } } }

mediniGetOpposites for a newly created trace

medini_1005438711

Hi,

Does mediniGetOpposites work also for newly created trace for example between a failure mode and a failure entry (i.e. right after a new failure mode is added to an attached FMEA)?

The following code fails for the first run, but works for the 2nd run.

var componentEntry = fmea.components[0];
var element = componentEntry.element;
var newFM = findOrCreateFailureMode(element, 'new Failure Mode' );
console.log( newFM.mediniGetOpposites('element').size() ); // this returns 0 instead of > 1
var failureEntry = newFM.mediniGetOpposites('element')[0]; // this fails for the first run as mediniGetOpposites returns null

Regards,

Toru

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1036016653

Hi Toru,

w.r.t. to "flush" there is a synchronization call available:

https://medini.freshdesk.com/support/discussions/topics/1000092034

May be it helps, bye

Peter

All comments

medini_1005438711

Is there a kind of "flush" function to reflect the model change immediately?

medini_1036016653

Hi Toru,

w.r.t. to "flush" there is a synchronization call available:

https://medini.freshdesk.com/support/discussions/topics/1000092034

May be it helps, bye

Peter

medini_1024169437

Exactly, thanks Peter! Just an additional explanation for Toru: creating the failure mode will not immediately create the FailureEntry in the worksheet, that is typically done at the end of the transaction, so the end of the script. To do that *within the lifetime of the script* you have to synchronize the worksheet as Peter wrote.

Happy Scripting

Jan

medini_1005438711

Hi Peter and Jan,

Aha, the keyword was "synchronization", thanks for the hint!

Regards,

Toru