We made a change in the December 5th-release (documented in release notes), it is no longer possible to change the order type of an order which has been finished or invoiced. This was a bug in BNXT, and inconsistent with behavior in Visma Business.   ... View more

If you get a guid with format "companyId.guid" in filePath the document is in Fileservice. Anyway, this processing returns documents regardless of storage location. Add args: {returnFileBytes: 1} to your mutation, I suspect it is missing? ... View more

@tommy nilsen @Florian Haase Use the viewDocuments-processing to fetch the document, it should be available in all relevant tables. The processing downloadIncomingDocument downloads documents from AutoInvoice to Business NXT🙂 ... View more

Yes, check if the voucher no. control is enabled in the company information table. ... View more

@jakob_sdf I am not able to reproduce the issue when I test with your mutation, so a little hard to tell based on the given info. The mutation in itself works just fine, but I would skip the lineNo from the input, as it is not necessary when you create new vouchers.  No need to use the insert row option in the UI, you can just start in the first column (Ver.nr.) on the new line, the insert-options are meant for inserting line in between the exisiting.  ... View more

@kashyap You have to fix the first error, the given value date is in conflict with the current suspension date for the company, prohibiting the batch creation, which is key to the rest of your mutation. Check the current suspension date by running the processing "Move suspension date" in the company information table. Then adjust your suspension date accordingly. ... View more

@iizy It seems this post should be on the Visma Net developer forum, please post it there.  ... View more

Hi @iizy My suggestion is that this is due to the use of crossReference, which triggers a lookup in open customer entries, and fetches the corresponding customerno to credit. Hard to avoid I think, but you can cancel out the credit posting by sending in "creditAccount: 0" somewhere after crossReference. Keep in mind that the input sequence often matters in BNXT.  ... View more

Hi @Magnus Vadla  I'm not able to reproduce with your example, so I am inclined to think the result depends on something in the company data.  It should not be necessary to set the accountType, but something leads to the assumption that 7519 is a supplier for some reason.  NB! Be aware you are using a deprecated way of suggesting voucher numbers.  ... View more

@Marius Bancila I think this is a need for the "groupBy"-feature to get the balance of different account/orgunit-combinations.  ... View more

@Florian Haase Sorry, I know, the "Reply"-button in the UI here changes to "Accept as solution" once it is pressed, and I happened to click it once too much apparently.  ... View more

@Florian Haase The TaskOverview-table is not in use in Business NXT, so you will not be able to get the desired outcome. What you see in the UI is generated based on the other TaskOverview-tables, and not directly reproducible through the API to my knowledge. Is there a use case for it?  ... View more

@Florian Haase Would this work for your purpose?  query taskOverview($custno: Int) { useCustomer(no: $custno) { taskOverviewDefinition { totalCount items { taskOverviewNo description } } } }   ... View more

Hi Stig There is a community thread on this already, it's up for discussion. Feel free to share your thoughts there.  At the moment all entries from the API have origin = 1.  ... View more

@David Tandberg-Johansen Sorry, "Accept as Solution" is pretty close to "Reply"😬 The current backend version is 18.10.something. Not necessarily a version available for VB.  If the issue is related to the BNXT API, feel free to report it here, and we'll investigate.  If it is more of a VBS-related issue, the Developer forum for VB is the correct channel.  If you think it's an application-issue on VB/BNXT, it should be registered as a ticket to support in the Partner portal.  ... View more

@danielboylan It is discount in % or discount as an amount (or both if you want), there is no calculation between these fields.  ... View more

@Eivfjeld That's not exactly regular user access I would say. To be more specific: On customer level: BNXT role - Application access (without it you will not see BNXT in Home, nor have UI access).  On company level: BNXT role - System should do (if it is the default access group - we do not control what customers/partners do with access groups). The rest of the provided roles above can be removed, they are not relevant in this context. Remember to log out, and back in after access changes in Admin.  ... View more

@AndreasDevDotNet Support for webhooks is still work in progress, currently planned timeline is Q4.  ... View more

@danielboylan Visma XML as format was abandoned many years ago, and has not been maintained, so no, it is not supported.  The orderDocument table is probably your best starting point. Different names in GUI as in Visma Business is not yet supported, can't say when (or if) it will be.  ... View more

@David Tandberg-Johansen I believe you have to update the batch to move the counter at the moment (what @omelhus also refers to I suppose). That behaviour deviates from default manual journal entry, so we should probably have a look at it. I'll get back to you after some more proper testing.   On the "auditor's order": There is no rule that makes it mandatory to keep the same voucher number  inside a batch. Try to invoice more than one invoice at the time, and you'll see what I mean. ERPs differ to a certain degree on how numbering works and what the unique updated voucher identifier is, and auditors sometimes tell customers things for their own convenience I suspect🤔  ... View more

@David Tandberg-Johansen  Yes, in this case the three lines (first and second balances) give two voucher numbers. Change the amount to balance across the three lines, and the voucher no remains the same. Normally, the balancing of voucher numbers is the desired outcome. Run a new batch, and the numbers will increment as they should.  If you want to set the same voucher no for all vouchers in a batch without suggesting, query the next from the desired voucher series, and set it on all vouchers inside the batch. Maybe as a batched request, with the query first, and the mutation second. I don't have an example for that at the moment.  ... View more

Hi @Eivfjeld Regular user access to the company in Admin will give API-access in a user-context for instance here.  If you require access through the service-API, you need to follow these instructions. Nothing to do in Admin in this scenario.  ... View more

@David Tandberg-Johansen As far as I can see, both the alternatives described in the documentation should work. I agree that the first example is not the best, it was probably written before the suggest-option came to life. We've had more than one way of suggesting values, the deprecated one is marked as such in the documentation. The latest suggest method is here, also used in the alternatives mentioned above.  As for sometimes having the same voucherno and sometimes not, it should depend on whether the voucherno balances or not. As long as the voucherno does not balance, the same voucherno is used on the next line. When the voucher is in balance, the next voucherno is suggested etc. I usually use this example to test batch/voucher-creation with suggested values, try it out and let me know what you think:  mutation CreateBatch ($cid: Int, $batchId: Int = 0) { useCompany(no: $cid){ batch_create( values: [ { voucherSeriesNo: 1, valueDate: 20230926 description: "Test suggest" }]) { affectedRows items { batchNo @export(as: "batchId")} } voucher_create( values: [{ batchNo: $batchId valueDate: null voucherDate: null voucherType: null voucherNo: null text: "first line" amountDomestic: 1300 creditAccountNo:4300 }, { batchNo: $batchId valueDate: null voucherDate: null voucherType: null voucherNo: null text: "second line" amountDomestic: 1300 debitAccountNo: 4300 }, { batchNo: $batchId valueDate: null voucherDate: null voucherType: null voucherNo: null text: "third line" amountDomestic: 500 debitAccountNo: 4300 }]) {affectedRows items{ batchNo voucherNo } } } }   ... View more