API Forum

This forum is in read-only mode.
Please refer to our API support in case you have any questions.
We can be reached at api@e-conomic.com
e-conomic API developer forum

Issue with trying to create Employee data


Zedonk is encountering a problem with trying to create Employee data in the e-conomic system, with the following error:

 Invoice:IN-00974 (835171) **Error** 

Message:The element 'EmployeeData' in namespace 'http://e-conomic.com' has incomplete content. List of possible elements expected: 'CostPrice' in namespace 'http://e-conomic.com'. (id=1f176fc3-067c-4f35-a88b-80ca3e94398d) 
Target Site:Economic.Api.IEmployee Employee_CreateFromData(Economic.Api.Data.IEmployeeData) 
Stack Trace: 
 at Economic.Api.EconomicSession.Employee_CreateFromData(IEmployeeData data) 
 at Economic.Api.EmployeeUtil.CreateFromData(IEmployeeData data) 
 at Export_Syncronise.IzExportDestination.EconomicFindOrCreateEmployeeByName(String EmployeeName) 
 at Export_Syncronise.IzExportDestination.FindOrCreateInvoice(IzInvoice ZInvoice) 
 at Export_Syncronise.ExportInvoices()   

We have checked your documentation link and can't see this new field mentioned:

But when we look at the actual SOAP we can see this new field: 

We have just downloaded the latest version of the API DLL's from: 

But these don't mention the new fields when we interrogate the DLL: 


created May 31, 2013 by jacquik
0% Accept Rate
Q 1 A 0 C 0

4 Answers


Hey. We are having the same issues. It's not cool to fundamentally change a method construct that breaks existing integrations. At least the SDK should be upgraded as well. In defence of e-conomic, they actually released a working DLL in the release candidate branch on github. See https://github.com/e-conomic/eco-api-ex/tree/release_candidate. It works for us. Until further notice, it looks like we need to put this into production.

answered Jun 3, 2013 by oexenhave
The fix to this issue will be deployed to production Monday night (10.06.13). Until then, the workaround, mentioned by Søren, is an acceptable approach for getting things back to normal.
Second, we obviously apologize for inadvertently introducing a breaking change to our API. Consequently, we will internally handle this issue is a bug, and will introduce further tests to avoid releasing mandatory fields without notice.
Lastly, on a side note, I can also reveal that the introduced fields will be redesigned in the coming weeks, to more precisely reflect the full feature in the application - i.e. by distinguishing between before- and after cost price and allow access to the calculated effective hourly price.
answered Jun 3, 2013 by mortenanders
edited Jun 4, 2013 by mortenanders

The service has now been updated in production, so that CostPrice and SalesPrice on EmployeeData are no longer mandatory.

We, again, apologize for any inconveniences.
answered Jun 11, 2013 by mortenanders
The master branch in the SDK has also now been updated to fit the new service description: https://github.com/e-conomic/eco-api-ex
Furthermore, we have also taken the liberty to remove the release candidate branch, since this release makes it obsolete. 
answered Jun 11, 2013 by mortenanders
Visma e-conomic A/S