[TCArknight]

Thanks Mathias!

That pointed me in the right direction. I have a Lifepath component with a child entity, lpCustom using the LifepathHelper (a thing based on the LifepathHelper component).

  <!-- Lifepath Module -->
  <!-- form="lifepathgiz"> -->
  <entity
    id="lpCustom"
    form="lifepathgiz">
    <bootstrap thing="LifepathHelper"/>
    </entity>

  <component
    id="LifepathHelper"
    name="Lifepath Helper">
	  
    <field
      id="lpSpecExpr"
      name="Specialty Expression"
      type="derived"
	  maxlength="500"
	  defvalue="TRUE">
	  </field>
    
    <!-- build the expression strings based on tags -->
    <eval index="1" phase="Render" priority="5000"><![CDATA[
	  var expr as string

      ~ get the tags from the container for what Specialties are available	  
	  expr = container.tagids[Specialty.?,"|"]
	  expr = replace(expr, "Specialty", "thingid", 0)
	  
      field[lpSpecExpr].text = expr
	  
      ]]></eval>
    </component>

This seems to work fine. When I add a module (Street Kid), the lifepathgiz form pops up with the table to select the Specialty (and the list is correct based on the tags on the Street Kid module).

When a Specialty is selected (doing an autotag with Helper.Shadow) this error pops up:

Live state of gizmo 'lpCustom' is being tested during phase 'Initialization' at priority 10000 by pick 'Runner' (spcT2KRunner) before live state of parent pick 'lpT2KStreetKid' is resolved

The phase being tested is apparently on the SpecialTab component. When I remove that from the Specialty compset though, it pops the same aerror with a different "tested during" timing.

Is there something I'm missing or how is this handled for SR5 and the Life Modules?