Skip to main content
Solved

Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index


In trying to Export an ACH payment using FEDWIRE Payment Method, I am receiving the following error:  - Acumatica Cloud ERP 2021 R2 Build 21.214.0034

 

 

 

TRACE:

 

Error:    Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index     Send

Raised At: 10/13/2022 12:46:07 AM    Screen: AP.30.50.00        

 Details:

10/13/2022 12:46:07 AM Error:

Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)

   at PX.DataSync.ACHSYProvider.Export(String objectName, PXSYTable table, Boolean breakOnError, Action`1 callback)

   at PX.Api.SyMappingUtils.WritePreparedDataToProvider(SYProcess graph, SYMapping mapping, SYImportOperation operation, PXSYTable preparedData)

   at PX.Api.SyMappingUtils.ImportData(SYProcess graph, SYMappingActive mapping, SYImportOperation operation, SYMappingActive updated)

   at PX.Api.SyMappingUtils.ProcessMapping(SYProcess graph, SYMappingActive mapping, SYImportOperation operation)

   at PX.Api.SYExportProcess.RunScenario(String scenario, RepeatingOption repeatingData, Boolean breakOnError, Boolean refreshPrepare, PXSYParameter[] parameters)

   at PX.Objects.CA.CABatchEntry.<>c__DisplayClass21_0.b__0()

   at PX.Data.PXLongOperation.<>c__DisplayClass18_0.b__0()

Information:    Export optimization failed due to Bql delegate on view Payments     Send

Raised At: 10/13/2022 12:46:07 AM    Screen: AP.30.50.00        

 Details:

10/13/2022 12:46:07 AM Information:

Export optimization failed due to Bql delegate on view Payments

   at Serilog.Core.Logger.Write(LogEventLevel level, Exception exception, String messageTemplate, Object[] propertyValues)

   at Serilog.Core.Logger.Information[T](String messageTemplate, T propertyValue)

   at PX.Data.Api.Export.SyImport.GrowingTableBuilder.Create(PXGraph graph, SyExportContext context)

   at PX.Api.SyImportProcessor.ExportTableHelper..ctor(SyExportContext context, Boolean submit)

   at PX.Api.SyMappingUtils.ExportPreparedData(SYProcess graph, SYMapping mapping, Boolean breakOnError, Boolean newApi)

   at PX.Api.SYExportProcess.QueryPreparedData(SYMapping mapping, SYImportOperation operation)

   at PX.Api.SyMappingUtils.PrepareData(SYProcess graph, SYMappingActive mapping, SYImportOperation operation, SYMappingActive updated)

   at PX.Api.SyMappingUtils.ProcessMapping(SYProcess graph, SYMappingActive mapping, SYImportOperation operation)

   at PX.Api.SYExportProcess.RunScenario(String scenario, RepeatingOption repeatingData, Boolean breakOnError, Boolean refreshPrepare, PXSYParameter[] parameters)

   at PX.Objects.CA.CABatchEntry.<>c__DisplayClass21_0.b__0()

   at PX.Data.PXLongOperation.<>c__DisplayClass18_0.b__0()

   at PX.Data.PXLongOperation.PerformOperation(Object arg)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at PX.Data.PXThreadPool.RunItem(RequestItem item)

   at PX.Data.PXThreadPool.Run()

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()

 

Best answer by DConcannon

After further investigation I don’t think the export scenario warnings should be a concern. I have the same warnings with a working export.

 

View original
Did this topic help you find an answer to your question?

6 replies

DConcannon
Varsity II
Forum|alt.badge.img+2
  • Varsity II
  • 119 replies
  • October 13, 2022

Hi @RobMorris 

Has the export worked before, or are you just setting it up?  Is all the banking information setup for the cash account and the customers being paid? And according to the masks and validation expressions for the payment method?


  • Author
  • Freshman II
  • 10 replies
  • October 13, 2022

New setup. I had it working in a test environment cannot get it to work in live Environment, not sure what I am missing.

 

Payment Methods- 

 

 

Payment Methods - SETTINGS FOR USE IN AP

 

 

Cash Accounts:
 

 

 

Vendors - PAYMENT
 

 


  • Author
  • Freshman II
  • 10 replies
  • October 13, 2022

Found this is the Request Profiler along with the above error message :

 

 

 

at PX.Data.PXFirstChanceExceptionLogger.ProfilerFirstChanceException(Object o, FirstChanceExceptionEventArgs args)
   at PX.Data.PXDatabaseProviderBase.insert(Type table, PXDataFieldAssign[] pars, String commandText, Boolean switchAllowed, companySetting setting)
   at PX.Data.PXDatabaseProviderBase.Insert(Type table, PXDataFieldAssign[] pars)
   at PX.Data.PXDatabase.Insert(Type table, PXDataFieldAssign[] pars)
   at PX.Data.PXGraph.ProviderInsert(Type table, PXDataFieldAssign[] pars)
   at PX.Data.PXCache`1.PersistInserted(Object row, Boolean bypassInterceptor)
   at PX.Data.PXCache`1.Persist(PXDBOperation operation)
   at PX.Data.PXGraph.Persist(Type cacheType, PXDBOperation operation)
   at PX.Data.PXGraph.Persist()
   at PX.Data.PXSave`1.<Handler>d__2.MoveNext()
   at PX.Data.PXAction`1.<Press>d__38.MoveNext()
   at PX.Data.PXAction`1.PressImpl(Boolean internalCall, Boolean externalCall)
   at PX.Data.PXAction`1.Press()
   at PX.Api.SyMappingUtils.PrepareData(SYProcess graph, SYMappingActive mapping, SYImportOperation operation, SYMappingActive updated)
   at PX.Api.SyMappingUtils.ProcessMapping(SYProcess graph, SYMappingActive mapping, SYImportOperation operation)
   at PX.Api.SYExportProcess.RunScenario(String scenario, RepeatingOption repeatingData, Boolean breakOnError, Boolean refreshPrepare, PXSYParameter[] parameters)
   at PX.Objects.CA.CABatchEntry.<>c__DisplayClass21_0.<Export>b__0()
   at PX.Data.PXLongOperation.<>c__DisplayClass18_0.<StartOperation>b__0()
   at PX.Data.PXLongOperation.PerformOperation(Object arg)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at PX.Data.PXThreadPool.RunItem(RequestItem item)
   at PX.Data.PXThreadPool.Run()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

 


  • Author
  • Freshman II
  • 10 replies
  • October 13, 2022

In comparing the export scenario in both environments I have notice the error message “This object doesn’t exist.” , in the environment that is NOT working.

 

 

 


DConcannon
Varsity II
Forum|alt.badge.img+2
  • Varsity II
  • 119 replies
  • October 13, 2022

@RobMorris

Great screen shots.  Can you verify the Data Provider has the schema file attached and the Schema is populated/active

 


DConcannon
Varsity II
Forum|alt.badge.img+2
  • Varsity II
  • 119 replies
  • Answer
  • October 13, 2022

After further investigation I don’t think the export scenario warnings should be a concern. I have the same warnings with a working export.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings