Problem: When creatig a project task in the project task view in Visma.net and linking it to a project the projects lastModifiedDateTime is not updated. This causes a problem when using the lastModifiedDateTime in the API because we do not get the new project task when syncing.  Expected Behavior: Same behavior as when you create a task directly from the Project page THEN it seems to update lastModifiedDateTime correctly. Solves: Our sync problems caused by using lastModifiedDateTime. Today we have chosen to not use lastModifiedDateTime which makes us do a lot more requests towards Visma.net API. It would benefit both Visma.net and us to fix this.   ScreenId=PM3020PL (Creating & Linking from here it does not update lastModifiedDateTime) ScreenId=PM301000 (Creating from here updates lastModifiedDateTime correctly)     ... Visa mer

Today, when you register an prebooking, you only click on prebooking with the API and it is posted to an account and a subaccount that is always the same.   Above all in the construction industry, there are companies that need to be able to choose per invoice which account/code part they want to prebook on this invoice. This is not currently available in the API, but can be done manually in the system.   If this is prioritized and you manage to do this well, you will be able to be a strong player in the market to attract new customers in the construction industry. Others will also appreciate this solution. This means that your system will become more flexible when users want to make a so-called "pre-book".   See picture below for which fields are in Visma.     These are named APInvoice.PrebookAcctID and APInvoice.PrebookSubID. ... Visa mer