simPRO API Forum

It seems if a cost centre prebuild is edited for a job or quote inside Simpro, it creates a new temporary prebuild and changes the prebuild.id in the cost centre prebuild object?

Is this expected? It means we have no way of tracking back to the original prebuild. It doesn't really make sense why this would ever need to happen, unless its a relic of simpros old bad design.

If this is meant to be like this, why aren't we allowed to edit these temporary prebuilds? It would give us access to nearly all of the prebuild fields for close to zero effort.

Try this endpoint. /api/v1.0/companies/{companyID}/jobs/{jobID}/sections/{sectionID}/costCenters/{costCenterID}/prebuilds/{prebuildID}

Docs https://developer.simprogroup.com/apido ... 8e96acb6e8

That provides no more properties that can be changed vs the update method.

Hi there,

Its hard to pin-point your issue here, and it would help if you could provide the endpoint you are using. Cost Center Prebuilds are separated from Prebuilds as a whole. The reason there are separate instances of prebuilds within a cost center vs having the actual prebuild

(i.e. api/v1.0/companies/{companyID}/jobs/{jobID}/sections/{sectionID}/costCenters/{costCenterID}/prebuilds/{prebuildID} vs /api/v1.0/companies/{companyID}/prebuilds/ )

is to allow modification of that specific cost center prebuild instead of having the prebuild get updated for a specific cost center and having those changes then be applied to every single other cost center that uses said prebuild.

I see that you are having issues with updating the cost center specific prebuild and this is not the expected behaviour, it should be modifiable and if this is not the case then I would suggest you raise a support case here: https://helpdesk.simprogroup.com/#create-a-case

You can find more information on cost center prebuilds for jobs here: https://developer.simprogroup.com/apido ... uild-Items .

I also see you have mentioned this endpoint lacking properties that can be updated, and I would direct you to raise a feature request here if this was the case: https://helpguide.simprogroup.com/Conte ... portal.htm .

Or if you are apart of our partner program, you can relay this through those designated channels. If you haven't already, I would advise you sign up for our partner program, which you can do here: [email protected]
https://www.simprogroup.com/partners#become-a-partner

If you can provide the exact payload and endpoint you are using this may help clarify the situation and ensure that I am not mistaken for the situation you have outlined.

Thanks,

Our customers sometimes have their own names for our products that we must use on their invoices to be approved.

We planned to manage this through the API by editing the name of the prebuild on the cost centre. This is not possible via the /api/v1.0/companies/{companyID}/jobs/{jobID}/sections/{sectionID}/costCenters/{costCenterID}/prebuilds/{prebuildID} route.

I see what you're saying by cost centre prebuilds and actual prebuilds are seperate records, but there is no relationship from one to the other, it looks like when you edit a prebuild for a cost centre, it duplicates the actual prebuild in the prebuild table, applies changes and updates the prebuild ID to the duplicated record in the cost centre, and any relationship to the original prebuild is lost.

I was trying to understand if this is the expected design. That is I can only change the following properties for a prebuild, either globaly or on a cost centre:

{
"BillableItem": true,
"BillableStatus": "Billable",
"EstimatedTime": 0,
"FitTime": 0,
"BasePrice": 0,
"Markup": 0,
"SalesTaxCode": 0,
"DisplayOrder": 0,
"Discount": 0,
"SellPriceExDiscount": 0,
"SellPriceIncDiscount": 0,
"SellPrice": 0,
"Total": {
"Qty": 0
},
"IncomeAccount": 0
}

Hi there,

Thank you for the clarification on that, currently it is the expected behaviour that when a prebuild name gets edited through the UI that it will duplicate the original prebuild and make a new one as you said. I'll forward this onto my product manager as I recognise how this could be sub-optimal for some use cases. I'd also suggest liasing with a partner account manager and signing up to the partners program if you haven't already, as it is a much more efficient way to stay in the loop and request functionality.

From my understanding and after asking around the consensus seems to agree on that the architecture treats:
- Prebuilds & Catalog Items as templates/references (name comes from source)
- One-Off Items as custom, per-job items (name stored independently)

If you are looking to change the name of your item consistently, maybe a one off item could be more suited to what you are suggesting.

You can find more information about one off items for cost center items here: https://developer.simprogroup.com/apido ... 72db0b30db

Thanks,