Yes, original ReceiptQTY was 5 (As defined in the linked Purchase Order Line <orderQty>) PUT > .../controller/api/v1/PurchaseReceipt/000079 { "ReceiptType": { "value": "PoReceipt" }, "lines": [ { "operation": "Update", "lineNbr": { "value": 1 }, "transactionDescription": { "value": "UpdateReceiptQTY" }, "receiptQty": { "value": 7 } } ] }     Linked Purchase Order Line's ReceiptQty has also been updated accordingly. ... View more

We're able to add a Purchase Order Line with a non-stock item to the Purchase Receipt. 1) POST - Purchase Receipt > https://integration.visma.net/API/controller/api/v1/PurchaseReceipt { "receiptType": { "value": "PoReceipt" }, "supplierId": { "value": "00005" <Replace with your data> }, "date": { "value": "2021-07-12" } } 2) POST > .../api/v1/PurchaseReceipt/000079/action/addpurchaseorderlines { "purchaseOrderLines": [ { "orderNbr": "000132", <Replace with your data> "lines": [ { "lineNbr": "1" } ] } ] }   Reference "Purchase Order": Make sure, used non-stock item's "Require Receipt" flag is checked and Purchase Order Line > Account has a value.   Financials UI- Purchase Receipt ... View more

Hello,    How often do you receive the error messages ? When was the last time you've received, could you please send us ipp-request-id from the latest failed transactions ? Please also include your POST > Attachment snippet.    Thanks. ... View more

"operationId" has been implemented. (https://salesorder.visma.net/swagger/v3/swagger.json) ... View more

Hello,  to our knowledge, there hasn't been any change to the "document Type" in the model.   We'll check this out with the related team to make sure. ... View more

Hello Svein, you're sending the following values "postalCode": { "value": "9357"}, "county": {"value": "1029"} in the JSON. Default system defined, Post Code: "9357" is associated with City: "TENNEVOLL" and CountyID: "1029" is associated with City: "LINDESNES" therefore, regardless of the disabled validation, it gets its default values for the Main & Invoice Address(Currently we're unable to override them via the Initial POST request. We need to send consecutive PUT request with Main & Invoice & Delivery etc. address fields to override them. This has been reported and will be reviewed by the development team) Related screen > Financials ERP UI - Postcodes  <ScreenId=CS20401S> Post Code: "9357"  CountyID: "1920" City: "TENNEVOLL"   CountyID: "1029" City: "LINDESNES"   So if you'd like to set the addresses (Main & Invoice) with City:"FINNSNES",  Possible workarounds,  A) Update the corresponding Postcodes' definitions B) Use one of the defined Postcodes (9300,9305,9306,9307,9308,9309) with countyID: "1931" for the city: "FINNSNES"  C)  Currently, we're unable to override them via the initial POST request. We need to send consecutive PUT request with Main & Invoice & Delivery etc. address fields to override them. POST the base Customer then send PUT request.  PUT > https://integration.visma.net/API/controller/api/v1/customer/customerNumber     "mainAddress": { "value": { "addressLine1": { "value": "Leiknesveien 68" }, "addressLine2": { "value": "adr2" }, "addressLine3": { "value": "adr3" }, "postalCode": { "value": "9357" }, "city": { "value": "Finnsnes" }, "countryId": { "value": "NO" }, "county": { "value": "1029" } } }, "invoiceAddress": { "value": { "addressLine1": { "value": "Leiknesveien 68" }, "addressLine2": { "value": "adr2" }, "addressLine3": { "value": "adr3" }, "postalCode": { "value": "9357" }, "city": { "value": "Finnsnes" }, "countryId": { "value": "NO" }, "county": { "value": "1029" } } }, "deliveryAddress": { "value": { "addressLine1": { "value": "Leiknesveien 68" }, "addressLine2": { "value": "adr2" }, "addressLine3": { "value": "adr3" }, "postalCode": { "value": "9357" }, "city": { "value": "Finnsnes" }, "countryId": { "value": "NO" }, "county": { "value": "1029" } } } }         ... View more

After the fix, this will be working as described, auto-increment sequential numbers. (1-2-3 instead of 2-4-6) "lineNumber" doesn't have any effect in the POST operations, and it'll be automatically increased by as many lines as included in the transaction. ... View more

This can be inquired via GET > https://integration.visma.net/API/controller/api/v1/customerSalesPrice  based on Sales Prices <ScreenId=AR202000>   "Sales Prices" can be created only with one of the following types,  Price Type Price Code Base Empty (Check ItemID) Customer Customer ID Customer price class Customer Price Class ID   In this way, If the "Price Type" is e.g. "Customer" then the Price Code will be "CustomerID" and it'll be populated together with ItemId & Price etc. in the GET Response.  If the "Price Type" is "Customer Price Class" then the Price Code will be "Customer price class ID" which is referring to <ScreenId=AR208000>  Then, if you'd like to get all the sales prices defined for the inventories, GET .../api/v1/customerSalesPrice without any filtering parameter will return the full list.   In addition to that, if you'd like to get the "Customers" only have "PriceClassID=xxx", unfortunately this is currently not exposed via the GET Customer endpoint. To be able to do that, "PriceClassID" should be added to the Customer endpoint as a filtering parameter.    If this is what you'd like to have, we recommend creating an improvement case in the "Ideas" section in the community. ... View more

Hello Ole,    When Posting, entered "lineNbr" is not taken into consideration, and it is auto incremental. "lineNbr" field is used in PUT & DELETE operations wherever it's supported.  However, we confirm the issue with the  POST > https://integration.visma.net/API/controller/api/v2/journaltransaction  there appears to be an error with the flow since it increases the "LineNbr" by two when the JT created via the API.    This has been reported. We'll keep the thread updated on progress.   ... View more

Hello Jimmy,   could you please inform us about the specific module <screenID>  / Built-in report etc. that is available in the Financials ERP UI if you can receive the data as requested ?  ... View more

Hello Svein,  you could possibly disable the validations and retry.   In Financials ERP <ScreenId=CS20400S>   Example POST Customer Json:     { "number": { "value": "10623" }, "name": { "value": "TestCountyR" }, "status": { "value": "Active" }, "vatRegistrationId": { "value": "919573469" }, "corporateId": { "value": "919573469" }, "mainAddress": { "value": { "addressLine1": { "value": "Brauta 21" }, "postalCode": { "value": "6270" }, "city": { "value": "BRATTVÅG" }, "county": { "value": "1029" } } }, "mainContact": { "value": { "name": { "value": "Test Person" }, "attention": { "value": "Test Attention" }, "email": { "value": "testg@gmail.com" }, "phone1": { "value": "992888888" }, "phone2": { "value": "992888888" } } }, "deliveryAddress": { "value": { "addressLine1": { "value": "Ullavegen 61" }, "addressLine2": { "value": "7080555" }, "addressLine3": { "value": "XXX" }, "postalCode": { "value": "6290" }, "city": { "value": "HARAMSØY" } } } }       Output:   ... View more

Thank you for the confirmation. Although "Branch" field is visible in the "Example Value" part of the documentation, the field does not seem exposed via the "ProjectDto" & "TaskExtendedDto". This can be checked at the "Model" section.  The documentation inconsistency has been reported to the team. As soon as we have more information regarding the status of the case, we will share it here.   ... View more

Hello,    @jnemo wrote: Ok, so it seems api/CustomerInvoice includes Drafts when returning dunningLetterDate/dunningLetterLevel? That's true.   @jnemo wrote: I'm after Invoices with a DunningLetterLevel that is 1 where the DunningLetter also has Status Released. Is there a way of doing this? Or getting the list of the actualy DunningLetters? currently, it's not possible to filter the data based on "Dunning letter status".      This can be registered as a wish for improvement in the "Ideas" part of the community. ... View more

Hello Magnus,    1- Has multi-branch support functionality been enabled ? <ScreenId=CS100000>   2- Please make sure the user that has been generated a token with has the following roles in addition to <Financials User> & <Financials Administrator> (Please see the article Connecting your Visma.Net Financials company to the API section "3- Company access and rights" > 3.C )   3- Check the aforementioned roles in the Financials ERP UI and make sure they've been assigned to the user the token generated with. Users <ScreenId=SM201010> ... View more

Hello,   We're unable to reproduce the mentioned issue. Please review and send us the details of the following modules/steps with print screens. How do you fetch the Invoice A & B, is that a GET Specific Customer Invoice request ? Please send the URL.  1) Go to > Dunning letter history by document <ScreenId=AR408500> and check the listed invoices based on the customer. (Make sure the start date set ">=" 2021-01-26  based on Invoice "A" dunningLetterDate.)   2) e.g Customer Invoice: "00228" > Dunning Level: "0" > Does not show Dunning Information in the Customer Invoice:"00228"(ERP UI) and does not return the following information via the GET /api/v1/customerinvoice/00228 "dunningLetterDate": "xxx", "dunningLetterLevel": x   3- What is the company Customer Ledger Preferences > Dunning Settings <ScreenId=AR101000> ?    ... View more

The usage of the "LastModifiedDateTime" parameter exposed in the Journal Transaction V2 is different from others. So there is no "LastModifiedDateTimeCondition" and it's set ">=" by default when the parameter used.   This is Mandatory if ‘PeriodId’ is not provided. In your case, you've provided the PeriodId, so you can remove the "LastModifiedDateTime" parameter. ... View more

Thanks for letting us know Gerrit 🙂 Sorry, I've mistaken with "GeneralLedgerTransactions" so in that case please also remove the lastmodifieddatetime from your Journal Transaction V2 query. ... View more

Hello Gerrit,  releases can be followed in the "News" section also for sure by checking the swagger version tag. We've reviewed the company-id: 3001421 and we've seen that the new query structure wasn't activated for that company, it has now been invoked so that could you please try again ?    Also noticed that in your query,  "LastModifiedDateTime" value is 1900-01-01. This should be used with a date that matching with the data to narrow the scope of the data. And It is missing the "LastModifiedDateTimeCondition" parameter.     https://integration.visma.net/API/controller/api/v2/journaltransaction?pageNumber=30&periodId=202101&lastModifiedDateTime=1900-01-01&releasedBatch=true&pageSize=1000       "...ModifiedDateTime" parameters should always be used together with "...ModifiedDateTimeCondition".   > GET https://integration.visma.net/API/controller/api/v1/GeneralLedgerTransactions? lastModifiedDateTime=2021-09-10& (YYYY-MM-DD)     lastModifiedDateTimeCondition=%3E     Supported comparative operators for "DateTimeCondition"  (Those should be URL encoded in the query) > (%3E) < (%3C) <= (%3C%3D) >= (%3E%3D)  ... View more

Version tag has been added to the https://salesorder.visma.net/swagger/index.html -Status of exposing unique operation_ID for each operation is pending. ... View more

Hello,  this has been planned to be implemented in Visma.net Financials API updates for version 8.74.0 (November 2021) ... View more

Hello, we're currently working on a fix for this. As soon as we have more information, we will share it with you. Thank you for your patience and understanding while we addressed the issue.     ... View more

Please send the API Client ID  & Approximate Date/Time of the request/s to developersupport@visma.com   Could you please make sure that there are invoices in the company matching with the specified lastModifiedDateTime&lastModifiedDateTimeCondition ? ... View more

We can for sure check the situation once it has implemented and see if it's the most plausible solution, otherwise we can still look for the alternatives 🙂  ... View more