Bugfix with version 4.782 just released an hour ago: label printing would crash with a system error under following condition. Now repaired
- Part label configured to print a location, but part in question doesn't have a location.
Bugfix with version 4.782 just released an hour ago: label printing would crash with a system error under following condition. Now repaired
Heavy reworking on label printing
This version of c9 is a deep rewrite of label printing subsystem. Functionally visually changes are modest. Visual/functional changes:
Comprehensive list of Label commands
Parameterized commands can take form of either <key>=<value> or <key>(<value>). List below is written in <key>(<value>) format
Basic math operations are possible. e.g. 10+5/2. Mostly relevant for adjsize command
Strings must be wrapped in single quotes.
Command | Description | Example |
font | Font name | font(‘Arial’) |
size | Font Size | size(12) |
adjsize | And adjustment to apply to already set size. e.g. to make bigger or smaller | adjsize(+2) |
value | Hard code what the value is to be. | value(‘Test Motorcycles’) |
row | Row # to put item on | row(4) |
vertalign | Vertical alignment. 1=top. 2=center. 3=bottom | vertalign(2) |
textblock | Allow entry to word wrap | textblock(1) |
show | Make visible | |
hide | Make hidden | |
bold | make bold | |
italic | make italic | |
bolditalic | make bold+italic | |
left | left justify | |
center | center text | |
right | right justify | |
format | Clarion Language reformat | format(‘@n$12.2’) |
col | Justify column. 1= left. 2=middle. 3=right | col(3) |
style | Clarion Language font style | style(1) |
splitmerge | Forced gap close on word wrapping, in 1/1000th of inch. Used mainly for tall barcodes. | splitmerge(40) |
visible | Make item visible/invisible | visible(0) |
Example:
bold adjsize=*1.3
Step 1. Make sure you have Lusty setup as a franchise in c9
Spares -> utilities -> add / Edit Franchise.
If you cannot see lusty in the list. Click on button 'Add New Franchise'. Just two things to key in:
Step 2. Import price file for first time
Spares -> utilities -> import price file
Select Lusty from list of franchises in c9
Select 'C9 Central Repository Price files' from Source type
Pick Lusty in list of suppliers.
Click Okay a couple of times. Click 'Accept and continue' on disclaimer/ warning screen and you are done.
Includes DB changes you need to log all terminals out during upgrade
This version delivers two very heavy changes.
#1 cash basis GST reporting has been completely reworked. C9 activity report now only reports accruals basis txns. But on BAS report c9 now computes cash basis position by looking at accruals position and factoring in status of open AR/AP transactions at the time. Significantly simpler way to compute cash basis GST reporting.
#2 open invoice accounting is now finally fully here. Aged balances of debtors and creditors is now entirely computed based on open transaction status. This version will have some impacts on aged balances but final balances will still be the same. Generally it may cause aging to change and will change it for the better. Aftefacts you see like this: 90days: -1300, 60days: +1300 will now generally disappear as the underlying mechanisms that trigger this when using brought forward do not but design apply with open invoice. Manipulation of aging can now only happen by manipulating what transactions link to what. In new c9 the only way to influence aging is to change linking between txns.
Other changes
Includes database changes you need to log all terminals out during upgrade
Misc Changes
Payroll Changes
This version includes a wide number of payroll changes to better support single touch reporting requirements and scenarios. It includes a working implementation of STP that connects to ATO EVTE platform only and is able to meet ATO's conformance testing requirements. This version of STP is not yet production ready and functionality is disabled by default. Future versions will enable as soon as c9 passes their verification process, which is currently pending on the ATO to get back to us.
Specific Payroll changes:
Includes DB changes. You need to log all terminals out during upgrade
Single touch payroll is a requirement to send payroll information to ATO. It applies to everybody after July 1 so it applies to dealers who use c9's payroll module.
STP is a train-wreck. C9 currently doesn't have a working STP solution. I am dedicating all my time to solving the problem. I am confident I will solve the problem and I have 3 possible solutions being developed in parallel. Whichever gets finished first will be the one c9 will intialy use. I currently do not have a timeline for delivery. Delivery by July 1 is possible but not certain.
STP reporting is conceptually simple. It is essentially a payroll summary plus some other simple additional information that needs to be submitted with each payday. Collating this information is easy and the work to collate it took less than a day to engineer and the supporting code already exists in latest version of c9.
The problem is getting the data to the ATO. The ATO expect the data to be transported to them across a formidably complex technology stack typically used only by massive enterprises tamed by teams of dedicated computer programmers. In their own recognition of how impossible the task is for small operators the ATO developed a plan b) for people like c9. The problem is their plan b) is not working.
Update #1: just made contact with a new possible vendor and looks really promising. Putting option 1) back on the table for completion prior to July 1.
Includes database changes. You need to log terminals out during upgrade
Single Touch Payroll
This version includes first iteration of single touch payroll export. The implementation is untested (test lifecycle painfully slow). C9 implements STP via a 3rd party: singletouch.com.au. C9 will emit a CSV file you import into single touch in order to meet your reporting requirements.
Specific changes:
C9 now includes ability to generate bulk of reporting needed for Op2Ma
To access:
The more comprehensively you use c9 the more data can be meaningfully reported. Some new changes to c9 especially to help