We are performing global succession and we have increased the default to 10,000. However the system times out when we try to peform global succession for a commonly used material such as water. We understand that performance my be impacted, but we are unable to perform them in small groups because the system only shows a message that you are trying to perform global succession on more then 500 items. Any ideas on how to increase the amount before the system times out when performing this process or other methods to accomplish this task without manually touching each formula spec.
<add key="GSM.GlobalSuccession.MaxGlobalSuccessionSpes" value="10000"/>
<add key="GSM.SmartIssue.MaxAffectedSpes" value="10000"/>
<add key="GSM.SmartIssue.MaxSelectableAffectedSpes" value="10000"/>
If you experience a system time out when you run global succession, have you considered to extend the system timeout value?
Please try to add the following section into the <system.web> section in the Web\Portal\web.config
<httpRuntime executionTimeout="43200" maxRequestLength="104856" />
hope this helps.
We don't recommend going beyond 500 and can't guarantee the system will perform. As with everything there is always an upper limit, so if your total number of replacements is in the 10,000s you'll need to do the replacement as part of a data migration project with db scripts.
Global Succession uses stored procedures to retrieve the target specs and update the parent specs. You can take a look at those and use them if you want to orchestrate this manually. If you look at the Reg web.confg file you will see all of stored procedures used under the <SuccessionSpecType nodes.
Hi Jason. The majority of the code for this is done in DB stored procedures, so you could see all the logic and what tables are being updated. For example when replace a Material in a Formula, the xsp_MatInFormSpecGblScsnUpd procedure is used.
Please remember to be very careful with these kind of changes. You should back up the DB first. Also these changes should be made for non-material changes only, meaning nothing important has changed on the new spec. So no changes that could effect the nutrion, compliance, labelling, etc...
This change does not update the basis and it does not recalculate anything, it just swaps the spec.
If there is a change that is more impactful, you should use Smart Issue.
Hope this helps.