https://communities.bentley.com/products/geotech-analysis/f/forum/210142/what-order-should-g_i-embeddedbeammat-for-embedded-beam-row-properties-beI have the following line g_i .embeddedbeammat(( &quot;MaterialName&quot; , deadman_material_name ),( &quot;E&quot; , deadman_E ), (&quot;Width&quot;, deadman_width),( &quot;w&quot; , deadman_unit_weight ),( &quot;PredefinedBeamType&quot; , 2 ),( &quot;Lspacing&quot; , deadman_spacing ),( &quot;SkinResistance&quot;en-USTelligent Community 12https://communities.bentley.com/thread/636791?ContentTypeID=1Tue, 02 Mar 2021 17:41:20 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:1005249e-1863-45c8-8def-73e48217d5d2Stefanos Papavasileiou<p>Dear Iman,</p> <p>Indeed, you are close, but missing one parameter that is computed based on the width, which is the area.</p> <p>When using Python scripting, we need to define all linked parameters so if you add&nbsp;(&quot;A&quot;, deadman_area) the command should be successful.</p> <p>The moment you open the GUI (graphic user interface) the command is fully executed which then correctly computes the area in the background, leading to a valid material.</p><div style="clear:both;"></div>