Is there a way to update parameter of data provider from import/export methods?

Hi @twagner 

The data provider parameters are typically used to store static values which are set prior to the execution of a process or report, so directly updating these parameters within the export method may not be straightforward or recommended.

As a workaround, you could consider storing this "number of documents processed" counter in a custom table or DAC field. In this case, every time the export is successful, you could simply increment this counter and then save the updated value in your custom table. Then, in your data provider, you could retrieve the value from this table to use in your queries.

Here is an example of how you could implement this:

1. Define a custom table: First, you would create a custom table (let's call it ProcessedDocumentCounter) with at least two fields: CounterID and NumberOfDocuments.

2. Update the counter: In your export method, you would query this table to get the current count, increment it by one, and then update the table with the new value. Here is a rough example:

// Get the current counter
ProcessedDocumentCounter counter = PXSelect<ProcessedDocumentCounter,
        Where<ProcessedDocumentCounter.counterID, Equal<Required<ProcessedDocumentCounter.counterID>>>>.Select(this, "DocumentCounter");

// Increment the counter
counter.NumberOfDocuments += 1;

// Update the table
ProcessedDocumentCounter.Update(counter);

1. Retrieve the counter in your data provider: Finally, you would modify your data provider to retrieve this counter value and use it in your queries. For example:

public class MyDataProvider : IDataProvider
{
    public void Initialize(string name, IDictionary parameters)
    {
        // Retrieve the counter value from the database
        using (PXDataRecord record = PXDatabase.SelectSingle<ProcessedDocumentCounter>(
            new PXDataField("NumberOfDocuments"),
            new PXDataFieldValue("CounterID", "DocumentCounter")))
        {
            if (record != null)
            {
                int counterValue = record.GetInt32(0);
                // Now use 'counterValue' in your queries...
            }
        }
    }

    // Remaining methods...
}

Just remember to handle transaction rollbacks and error scenarios properly to ensure your counter remains accurate even if an export fails.

Thank you for your answer @davidnavasardyan09 ! Would there be an easy way to use a Numbering Sequence in Acumatica for this purpose? Then there’s no need to create custom table and already has a screen built for it for a user to potentially modify it. Are there any helper classes or methods in Acumatica for numbering sequences?

Hi @twagner were you able to find a solution? Thank you!