dont update full assembly

[mitoborecek]

I have assembly - all works with rules. But some parts dont move after all changes and finish rules. Only when I click to space and made "drag and drop" move and then part move on right place itselfs.

[WCrihfield]

Hi @mitoborecek.  Do you have any lines of code in your iLogic rules that will update the assembly after changes have been made?  If you click the update button after you rules have finished running, but before the 'click in space or drag and drop', to see if that makes the components move to their proper positions.  Do you have your settings set to 'Defer Updates'?  (Application Options > Assembly tab > top option)

[mitoborecek]

sorry my fault. I have to click and "make drag and drop" some part in assembly, but every part is joint to something (they didnt move), only mentioned part

[JMGunnar]

1.Do you use vault ? 

2. Any assembly component that's not have the right revsion/status  ?

Best Regards JM Gunnar

[mitoborecek]

1. dont use vault

2. revision/status? After "drag and drop" all parts (about 2-3) move on right place

[WCrihfield]

Hi @mitoborecek.

You did not really answer any of the 3 questions I asked you.

1. Do you have any lines of code within any of those iLogic rules that you mentioned that are for updating the assembly after changes have been made?
2. After you run the rules, but before you try to drag & drop anything, have you tried just clicking on the Update button (Manage tab > Update panel), to see if that will cause the components to move to their correct positions?
   1. If you have tried that, then what was the result?  Did they move to correct locations, or did they stay in wrong locations?
   2. If the Update button did not work, then have you tried using the Rebuild All button, to see if that will cause them to move to their correct positions?
      1. If you tried using the Rebuild All button, then what was the result...did it work, nor not?
3. Do you have your settings set to 'Defer Updates'?
   1. That setting can be found manually in the Application Options, on the Assembly tab, the top option.

Knowing the answers to those questions may help us understand what is going on, so that we can help you fix the problem.

[mitoborecek]

1. yes

   1. Component.Visible("SB:1") = MedziStena1

   2. odsadenieSB = GoExcel.CurrentRowValue("medzistena")

2. yes, no
   1. stay on wrong locations
   2. same
      1. no
3. yes

[WCrihfield]

OK, thanks.  Well those two lines of code you mentioned there are not really for 'updating' the assembly specifically.  What I was talking about was something like one of the following:

(used at/near end of rule, for immediate update)

iLogicVb.DocumentUpdate

or ILowLevelSupport.UpdateWhenDone Property (used at/near start of rule, to cause update when rule finishes)

iLogicVb.UpdateWhenDone = True

or Document.Update (where the variable 'oDoc' represents the Document object you are working with)

oDoc.Update()

or Document.Update2([AcceptErrorsAndContinue] As Boolean) 

oDoc.Update(True) 'True means accept errors and continue

 or Document.Rebuild() 

oDoc.Rebuild()

or Document.Rebuild2([AcceptErrorsAndContinue] As Boolean) 

oDoc.Rebuild2(True) 'True means accept errors and continue

I usually include something similar to one of those lines of code above at/near the end of most of my iLogic rules, to make sure that the document that the rule is making changes to gets updated after the changes have been made.  However, it sounds like you have already tried the Update and Rebuild All buttons in the user interface after running your rules, and they do not work to cause the components to move to their proper locations.  So, something must be going on.

From your last answer above, it sounds like you do have the 'Defer Updates' setting turned on.  As you may know, that prevents components from moving, even after constraint value modifications, until you manually perform a document update.  Then the components will move to the locations they are supposed to be, according to the constraints.  This sounds very much like what you are describing, but it sounds like some are still not moving, even after a regular Update or Rebuild.  That is very odd.  Are you using 'skeletal' modeling techniques?  Do some of your model files have other models 'derived' into them?  If so, are some of those models that have derived models in them, also derived into other models?  If so, the 'update system' may be loosing track of the second layer of 'derived in' stuff, not sure.