For my final blog, I will like to wrap things ups with particular things I have caught up on and what needs work in the coming days before the final application is ready
-
-
Over the past several days i have been considering the interface of the application, particularly to provide feedback upon making a request so the user knows what information has been posted and if it has been successful One advantage to shifting to an mvc architecture is that the controller can request a specific view for conditions such as the request being successful or not.
-
Since the previous blog I’ve spent some time considering the state of security of my applications Several pieces of stored information in particular concern me
-
Over the past week I have been learning more about the Oauth2 authentication process - the system used by xeros login. Thought I’d take an opportunity to record what I know to further cement the process in my head.
-
One concern which recently came to mind is how the web application performs when accessed by multiple users simultaneously. In theory there will only ever be a single user at a time but will additional users cause system instability? Multiple users modifying the same JSON variable could result in the invoice being inaccurate or produce erroneous invoice requests. Although, given the scope of blueberry IT the program should be run by a single client once per month. But mistakes can happen. In a future blog I will be exploring
-
issues understanding the xero wrapper
-
I’ve been having issues porting some of the functionality from .net framework forms to .net core. One particular issue has been getting OleDB to work in the new project.
-
I have begun playing around with the Xero API using their Xeronetstandard (https://github.com/XeroAPI/Xero-NetStandard) wrapper This has seen mixed results, following the tutorials available on xeronetstandards github repository I have successfully been able to complete xeros authorization process to create a connection and login to retrieve an api access token
-
As of a couple a weeks ago, following the lock down announcement blueberry IT has pulled the plug on its physical office as all non-essential services are required to be closed, However the team is still working remotely and, I have been directed to continue working on the invoicing project. I’ve been working on my CSV tool to handle data from CSP spreadsheet As of now, it seems to be functioning in the way I want it to, renaming necessary fields, renaming fields and entering static data(Eg tax amount, account number) I’ve also included functions to
- generate a unique id number for every invoice and save a record as persistence (Text file at the moment, best practice would be a database as record is less volatile)
- Generate the invoice data (1st of following month)
- Generate the due date (20th of following month )
-
All settled in now, I have been wrapping around how i need to manipulate the invoice data Pulled from BlueBerry’s provider into the format required by the xero API.
-
This week, I was hoping to join the BlueBerry crew at their office. However, due to my less than stellar communication I missed Richard while he was in Nelson. He plans to get me acquainted with the workspace and further details this upcoming Tuesday, when he returns.
-
This is my first post using jekyll for my project blog.. Now that it’s working (I think) I have been accepted for work placement at BlueBerryIT This Blog will be used as a journal to provide evidence for what I am doing with my time there as per course requirements