[Released]Creating Completed Quotes

[ThomasPollinger]

We are currently experiencing some confusion when importing data for completed quote and job pairs via the API. We are currently stumped while performing the following the process.

• Create quote with status converted to job and IsClosed true

• Create a job with updated information such as scheduling information and completed status + stage

what we are expecting is for the quote to be closed but the IsClosed flag appears to still be set to true when querying the quote via the API, even after using a update patch call. This results in quotes appearing in the open column when we would expect them to be in the closed column.
The only way we have found to close the quote without archiving is to convert to job which will duplicate the job or cause us to have to convert to job rather than using the multiple endpoint to create jobs en mass.

Is there a way to mark the quotes as complete perhaps by a configuration tweak or an endpoint that we are unaware for example an endpoint that can associate quotes and jobs?

Any insight on how this can be addressed would be appreciated.

Regards, Thomas

[Sindre]

Hi ThomasPollinger,
Thank you for reporting this.

We will test and investigate why it is not being updated as expected when using patch.

You can use patch to update the "Stage" of the quote that has been converted to "Complete" but that will not change the "IsClosed" value.

The standard way if doing it is using /convert/ on the quote endpoint as you mention but that is not supported for multiple.

Regards

[Mike_Roberts]

Hey Sindre, I thought I'd jump in here and prompt a conversation.

/api/v1.0/companies/{companyID}/quotes/{quoteID}/convert/
If you can't convert the quotes to jobs in simPRO you might be able to use a custom field to store information you need but they won't be physically linked in simPRO.

We know we can convert a quote to a job, but we are migrating from Salesforce to simPRO via custom ETL tooling over the simPRO API.

The tooling has what we see as a logical order of operations:

- Loads Customers
- Loads Sites
- Loads Quotes
- Loads QuoteLineItems
- Loads Jobs
- Loads JobLineItems
- Load JobAttachments

We can't be the first team to come along and say, "We have Quotes, and we have Jobs, and they are related and already exist." It's baffling that we are unable to close a completed Quote via the API.

IE There is an undocumented restriction to the API preventing us from putting a Quote into a state we'd expect.

Surely there must be a way to do this? How have other companies solved for this problem? Thank you!

I'll unpack some more context in case it prompts an idea

- We are importing many existing quotes from a large Salesforce system
- Many Quotes which have related Jobs entities.
- We want to create a quote, set it's status to something logical (complete / and closed).
- We want to then Create the subsequent related Job.
- We are unable to do this

[Sindre]

Hi Thomas,
We've done some investigation on patching the "IsClosed" value.

It you include "ArchiveReason" as an integer in your request is should work as expected setting a Quote to "IsClosed" = true.

You can find the archive reasons configured in your build with this endpoint:

https://developer.simprogroup.com/apido ... 6fe4a1f44b

Code: Select all

/api/v1.0/companies/{companyID}/setup/archiveReasons/quotes/

We will update the endpoint to inform of this.

Regards