A few problems with Sage Link to Actinic, some we've discussed before and a new one...
(1) Should a product have a zero value then Link refuses to export it as the line value is nil.
Ok so why would you ever want to do this you ask? Well it's not all just about sales it's also about supply, sometimes you want to issue free stock or keep your offices stocked up with say pens from the warehouse. This is simply acheived by either setting that product at zero value and only showing on certain price lists or having a schedule which multiplies by zero...
(2) Overflow errors, these are becoming a right pain in ass ... excuse my Transalvanian but we've been at these gates for months.
The problems seems to be related to anything not of the norm. As an example you make a small change in Sage or Actinic to a linked product or client, or if you try and sell a product made up of components and the product price. With the second example you can reindex your data all week long and it'll still overflow on export...
(3) Customer changes in Sage, linked logic.
The customer records seem to be compared in Link via the string for the customers actual name rather than the external reference. What happens is that should you alter the customer name a new one is created, rather than replaced in Actinic (even with update selected) and thus when you upload, a fulaccount.fil error is received.
Not to seem rude but rather than tell us the development team are looking at this, do you think they could stop looking and start fixing these long running issues? I have a vase on my desk, I'm looking at that ... nope nothing happening...
(1) Should a product have a zero value then Link refuses to export it as the line value is nil.
Ok so why would you ever want to do this you ask? Well it's not all just about sales it's also about supply, sometimes you want to issue free stock or keep your offices stocked up with say pens from the warehouse. This is simply acheived by either setting that product at zero value and only showing on certain price lists or having a schedule which multiplies by zero...
(2) Overflow errors, these are becoming a right pain in ass ... excuse my Transalvanian but we've been at these gates for months.
The problems seems to be related to anything not of the norm. As an example you make a small change in Sage or Actinic to a linked product or client, or if you try and sell a product made up of components and the product price. With the second example you can reindex your data all week long and it'll still overflow on export...
(3) Customer changes in Sage, linked logic.
The customer records seem to be compared in Link via the string for the customers actual name rather than the external reference. What happens is that should you alter the customer name a new one is created, rather than replaced in Actinic (even with update selected) and thus when you upload, a fulaccount.fil error is received.
Not to seem rude but rather than tell us the development team are looking at this, do you think they could stop looking and start fixing these long running issues? I have a vase on my desk, I'm looking at that ... nope nothing happening...
Comment