Sage 100

I have an existing customer using Knowledgesync. They have a single report with grouping by salesperson which shows the sales this month vs last year same month. The report runs great. I add to KS and change the output to PDF. My issue is that it appears to be setup correctly. I have a query against the AR_Salesperson and added that to the parameter of the report. Yet nothing emails. I'd expect to at least get a junk report but I never get an email (I added myself as the subscriber). Is there a helpful resource that isn't a 40-minute webinar recording that explains some of the details around how to set up a Crystal report to run and distribute to separate individuals?

I would like to know the answer. I ended up creating a separate report for each sales rep because I couldn't get the report to fire when I put in the SP code parameter.

I did what @DougHiggs did and set up a separate event for each rep. @JeffSchwenk says he has one event that goes to different salespeople but I think @DanBurleson helped set it up for him. @DanBurleson??

There's clearly something wrong with what I'm doing because when I test the report it claims to create the PDF in about 1 second and put it into an attachment folder. No email gets sent, no PDF is found in that folder and no error message is generated.

@DanBurleson is in the South Pacific, searching for Hobbits, I believe. :-)

This program is a throwback to the 1990's. Everyone swears it's the best thing since sliced bread then you try to do anything except a basic canned alert and it's twiddle thumbs time and no clue how to make it work. I guess it's off to the vendor to see what their options are for support on this BPOS.

Good luck. They will generally help, but I always get a scolding that this is the last time unless I get certified... Whatever that means.

This is a great learning experience. I find a lot of people tell you ""oh that's no problem"" until it is a problem. This is an orphan and I didn't sell the deal so I'll chalk it up as an arrow in my back and know not to accept responsibility for another KS as it seems poorly supported at best. Lot's of head nodding and ""should work"" but very little recent info on how to manage and setup.

I've always gotten GREAT support from Vineyard Soft.

@ThereseLogeais - Dan is not my man when dealing with KS. Yes, I do have alerts running that send to multiple salespeople. However, I use Access and PTQ's (**MUCH** easier than using linked tables) to connect KS to Sage. KS in the same book as SI and all the other third party enhancements. If you only do a one off, then it is much easier to sub the work out to someone doing it more frequently.

Someone called it

Burst reporting is very simple to configure with Visual Cut... just sayin'.

What if you are an end user. Do you have to be certified?

I just did my first Visual Cut setup last week. Works great, at 10% of the price of KS. Great if you don't need alerts.

VC can do alerts... just not ""new / changed record"" type queries.

The problem I have is the orphan already owned KS and someone (or several someone's before me) setup a few dozen KS. So moving them is not a great option. Otherwise, i would have used VC since I am not working on a real-time report.

What I usually see in this case is that you have setup KS to use KLF to create a link file (Access Link File) but the Crystal reports that run are running with SOTAMAS90. You would want to change crystal to use the tables from the KLF file and the problem goes away.

I really like KS and I think it works great. I am excited about the rewrite that is due out in Sept or so. I am sure it will come with it's problems but I would think it will fix some of the wired issues/steps that you might have to take.

Some other KS reports seem to be running off SOTAMAS90 so I'm stuck. KS sent a lengthy list of try this via email which wasn't helpful.

Why are you stuck?

In the setup for the connection what is the ODBC Data Source Name? Is it using a SOTAMAS90 DSN or the KLF DSN?

From my co-worker: They need to make the crystal report parameter only pull one customer at a time then use knowledge sync to run it out. The reason they aren't getting anything, at least at a guess, is that the crystal report doesn't know how to handle what is being passed. They should be able to check the monitor and find that there was an error there.

Thanks - Todd logged in and looked at this setup. Turns out that it was the Event Folder ODBC. He created a new folder to use the customer's SQL mirrored tables and we seem to be on the right track now. Thanks Todd!

Visual cut is the way to go. 90minds needs to do a webinar on it. . it is very powerful. Here is a link to the manual. It can do almost anything. http://www.milletsoftware.com/Visual_CUT_User_Manual/

A list is key benefits. http://www.milletsoftware.com/visualcutBenefit.htm

@JimWoodhead get me a contact, it seems like we've asked about this before from Millet Software.

@MoiraGoggin This is the developer, Ido Millet's email: ido@milletsoftware.com

Thank you @DougHiggs

@DougHiggs Ido and I have been exchanging emails and are trying to set up a group demo sometime after Meeting of the Minds. Thank you for the contact.

@MoiraGoggin Great. I would love to attend the demonstration.

Ido and I had a nice chat, he has some remarkable products besides Visual Cut. Very personable and extremely knowledgeable. He recommended that we have a member of our group (a 90 Minder) do the presentation. He said it would be 'more organic' if an ERP consultant presented how they use the product. With a little more chatting I got him to agree to attend the session and be available for the Q & A. So, here's the invite any 90 Minder or team or 90 Minders want to help present on Millet Software's Visual Cut, please let me know. We'd hold it after Meeting of The Minds.

@BethBowers mentioned @DanBurleson was searching for Hobbits. Not sure how he can concentrate looking for them......

No, not looking for Hobbits, but we did encounter, at our 1st hotel front in the south island of NZ, this unfortunate gnome with a knife in his back that may have been mistaken for a Hobbit.