New Diamond extended file format

This blog is in reference to the new extended file format which Diamond is releasing June 2008.

This is the announcement from the Diamond Daily.
*****************************
Important Announcement Regarding Upcoming Improvement to Extended Invoice Data Files

Acting on retailer suggestions, and effective beginning the week of June 1, Diamond will begin separating the Item Code from the Discount Code – which will now be noted in its own, separate field – in the extended versions of its weekly Invoice Data File.

Once this improvement is implemented, all additional fields in the Extended Invoice Data File will shift one space to the right. As a result, Diamond customers who utilize the Extended Invoice Data File are advised to adjust their inventory systems accordingly before the week of June 1.
*****************************

This response was written by me and posted at a forum for software developers who use Diamonds files in response to the previous announcement. The purpose of informing the CBPF users is so they will have a heads up on what will happen in June.

-------------------------

Cheryl,

Does this change accomplish anything for any of the readers of this forum? I'm sure all the programs out there have already made the correction within their software. Who requested this? How can making this change for two stores who are writing their own software, but causing problems for myriads (100s?) of stores which already have their software written, be a good thing?

If this was in the works before this forum was set up, it should have been announced as soon as the forum began so that the programmers could discuss the repercussions.

There ought to be a minimum standard announcement period for making file format changes. In reality 3 weeks is not sufficient. It should be in the neighborhood of 3 months minimum. It's possible that Moby, or ComTrac or CBPF or Hijinx has just come out with an update. It's also possible that one of the programs is in the middle of development towards its next update and 3 weeks is not sufficient time to make the change and complete the current updates and test.

It's also inconsiderate to expect a business which is in the middle of making updates to halt software production; go back to the last update; make the change; test; and release an update because of a change like this which accomplishes nothing, then make the change again in the update which the programmer is in the middle of.

The problem I see is that you are making the change to the extended file, but not the regular file. I encourage all CBPF users to sign up for the extended format, but I'm not sure if they have. Currently both formats are compatible from my viewpoint, but the extended provides the user just a little extra. But the new extended format will not be compatible with the regular format, therefore I'm about 90% sure some CBPF users will have problems whether I make the change or not. Am I to begin supporting two formats because Diamond decided to do something which should have been done when the file format was designed? Where are the test files containing the new format which I can use to test an update against?

If you're going to do this, you ought to also make the extended format an option which the user can choose from your site. That way, when a CBPF program isn't working, I can walk them through correcting the problem. The way it is now, they (or I) have to call you and get you to change the file format. It also obscures whether that is the problem as the user can't see on your site which format they are set up to receive.

My 4 cents.

And by the way, I will make more money from this change, but I'm against it because it hurts the comic stores. Their job is to help customers and sell more comics, not to spend time fighting a computer program which used to work, and now doesn't (and the change serves no purpose).

If this goes through and I don't have time to make the change and adequately test the update (which might be hard without a test file - Cheryl would you be able to provide one?), I'll have to post on my website to contact Diamond and request removal from the extended data file format to correct the problem. I know how many paying users I have, but I have no idea how many are using the free version of CBPF.

This comment is not meant to apply pressure. It is meant to inform of the issues at hand involved in this change with short notice.

(heads up) I will post this response on my site blog as a way of informing CBPF users so they know there may be problems in June and what the options are.

James
--------------------------------------------------------------

I look forward to any responses to this post.