About Marius Bancila

Robert_ITX · ‎26-01-2024

Great, thanks for letting me know.

Marius Bancila · ‎26-01-2024

The fix for this is now in production.

danielboylan · ‎26-01-2024

That's great, thanks!

Elling Bjåstad · ‎25-01-2024

Yes, if orgUnit1 is department and orgUnit2 is project, we want the ability to query general ledger transactions grouped by year, period, account, department and project, so that we get individual numbers for each combination of department and project. Edit: I looked briefly at the new groupBy feature, and it seems as if it covers what we need.

Marius Bancila · ‎25-01-2024

What exactly do you mean? Do you want to find whether it's possible to do insert, update, or delete for a particular table?

Florian Haase · ‎30-11-2023

Did you set this adding / removing of bit-values on a feature-list for future versions? We also see that this is needed.

ummya · ‎29-11-2023

Hi, I tried these two but but both giving me null query GetpaymentInfoFromCustomerTransaction { useCompany(no: 3867961) { customerTransaction( filter: { voucherType:{_eq:11} paidStatus:{_in:[3,4]} } ) { totalCount pageInfo { hasNextPage hasPreviousPage startCursor endCursor } items { customerNo orderNo invoiceNo voucherNo voucherType amountDomestic outstandingAmountDomestic cid dueDate crossReference paidStatus paidLast createdDateTime changedDateTime voucherDate } } } } ---------------------------------------------------------- query GetPaymentLines { useCompany(no: 3867961) { paymentLine(first: 1) { items { paymentNo lineNo currency : joinup_Currency { isoCode } supplier : joinup_Associate_via_Supplier { bankAccount country : joinup_Country { isoCode } } } } } }

omelhus · ‎29-11-2023

So you are saying that the functionality with suggesting values for entities using null is moot when you are using variables? When I create or update entities I almost exclusively use variables for inputs. Using parameters for all just doesn't make any sense. Please disable the suggest-functionality for entities in a variable, that is not enabled by suggest: { field: true }.

Robert_ITX · ‎28-11-2023

I see, thanks for confirming.

Marius Bancila · ‎14-11-2023

The GeneralLedgerTransaction table does have a key; however, it's a multi column key made of the voucherJournalNo and auditNo columns. In general, you can check the primary key columns for any table in GraphiQL (https://docs.business.visma.net/graphiql/😞 - open GraphiQL - write a simple query like this: - hover the cursor over the table (or any schema entity) that you want to explore: - click on the links (here, the connection) and explore it in the Schema Explorer (on the right) Primary keys are marked with [PK] and are always displayed first.

David Tandberg-Johansen · ‎07-11-2023

Hi @Marius Bancila Thank you for explaining the use

omelhus · ‎19-10-2023

🥳

Øyvind Årseth · ‎11-10-2023

@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.

David Tandberg-Johansen · ‎06-10-2023

Thank you

Marius Bancila · ‎05-10-2023

The fix for this has been deployed to production.

Marius Bancila · ‎29-09-2023

We have added support for including status code names in the response. Example: { "errors": [ { "message": "A record with the same primary key already exists.", "path": [ "useCompany", "order_create", "values/0" ], "extensions": { "data": { "status": 3, "status_name": "PrimaryKeyAssignmentFailed" } } } ], "data": { "useCompany": { "order_create": { "items": null } } } } You can read about it here: https://docs.business.visma.net/docs/features/errors#understanding-error-information

AndreasDevDotNet · ‎29-09-2023

Right now this client is something we use inhouse and it lacks documentation, I just wanted to check if there are any other people intrested. The only reason why we built this was that I could not find any other Linq providers for GraphQL that worked well, also I had a lot of free time this summer 🙂

danielboylan · ‎26-09-2023

Thanks for the followup Marius, I'll make sure to build bu query using "and"!

Marius Bancila · ‎22-09-2023

It works for me: mutation new_order_with_quotes($cid : Int, $ono : Int = 0) { useCompany(no: $cid) { order_create(values :[{ orderDate : null }]) { affectedRows items { orderNo @export(as : "ono") } } orderLine_create(values : [ { orderNo : $ono productNo : "101" description : "sample with \"quotes\"" } ]) { affectedRows items { orderNo lineNo description } } } } The response: { "data": { "useCompany": { "order_create": { "affectedRows": 1, "items": [ { "orderNo": 1058 } ] }, "orderLine_create": { "affectedRows": 1, "items": [ { "orderNo": 1058, "lineNo": 1, "description": "sample with \"quotes\"" } ] } } }, "extensions": { "vbnxt-trace-id": "000000000000000032440f34c79a852b" } } Result in front-end:

Florian Haase · ‎12-09-2023

Ok, That would also be a very rare scenario. But good to know. Thank you

omelhus · ‎08-09-2023

The limitation is enforced in the reverse proxy.

Florian Haase · ‎08-09-2023

The companyNo should be a 7 digit number which relates to the companyID from the Visma Connect plattform and not the internal Visma Business CompanyNumber. The advantage is that you can write API-integrations across different customers by using the Visma-unique companyNumbers.

David Tandberg-Johansen · ‎01-09-2023

Hi, I did get the same errors, what i found out it's the field externalId must have unique value. So when trying to save empty string, i think either the api or model looks at it as same value

Øyvind Årseth · ‎29-08-2023

@omelhus @AndreasDevDotNet In general, all wishes for Business NXT should be registered in the product portal for further evaluation. Strictly API-related topics are handled in this forum, while core/model-related issues should be in the product portal for a wider audience.

Marius Bancila · ‎25-08-2023

This is something else. Previously, you could not set a null, you were getting: "Argument 'values' has invalid value. In field 'textNo': [Expected 'Long!', found null.]" Now, you can. The fact that you get a runtime error is a completely different problem.

Marius Bancila · ‎25-08-2023

A fix for this is in production. hasNextPage should now return the correct value in all cases.

Dante Cavallin · ‎09-08-2023

Maybe I have to go the otherway around: query { useCompany(no: 9999) { picList ( filter: {pickListStatus: {eq:8}} ) { totalCount items { joindown_OrderDocument_via_Order{ orderDocumentNo documentType group3 } } } } } That should work I guess ?

omelhus · ‎21-07-2023

Would be cool if batch operations were executed in parallel, since they won’t share any data between them. And if you need something executed sequentially you could use the “inline batch”.

Marius Bancila · ‎20-07-2023

We have added support for batching requests. See documentation: https://docs.business.visma.net/docs/features/batches

Marius Bancila · ‎10-07-2023

This problem has been fixed and will be rolled to production this Thursday.

Re: Issue with filters/values when used in variabl...

Re: Issue with _suggest_interval when used in vari...

Re: Invoice changedDateTime not showing seconds

Re: Extraction of general ledger balance data on m...

Re: Get mutation type based on tablename

Sv: Bitflag columns

Re: Fetching and updating customers payment in Bus...

Sv: Problem with price when sending order lines as...

Re: URL for specific resource in GUI

Re: Syncing generalLedgerTransaction

Sv: Filter: _is_null AND _is_not_null

Re: Join in text from Text table in queries

Re: Business ERP Version and Integration between G...

Re: Filter documentType not when also filtering on...

Re: Filters on CompanyChangeLog

Re: Error-Codes

Re: Business NXT C# Client library

Re: When to get invoice from VBNXT

Re: Orderline - description "å"

Re: Escape wildcard %

Sv: Upload document to voucher (again)

Sv: Getting error : Unknown company.

Sv: Multirow create by GraphQL and return-handling

Re: No joinup_PickList on OrderDocument ??

Re: How to create a customer group via graphql

Re: HasNextPage

Svar: Filter on _joindown

Re: API Updates

Sv: Updating orderlines on order in one api call

Re: Missing null guards in joins?

Useful pages

About Visma

Contact us

Follow us