[philvan]

Hey all,

I'm experiencing a weird problem with Profile. Basically, our workflow is set up so that when a client file is properly inputted, it gets reviewed, where the reviewer looks over the file and saves the file as 'ready to print'. after a batch is created (ie 20-30 on client explorer), the reviewer logs off and another person logs on to print the files/efile it etc. now our problem is, the batch that was already built often doesnt show up! the printing person would have to go into each file again, and re-save them again (just a simple file, save as, no setting had to be changed! but still, for large batches, this is a bottleneck to the workflow) in order for the client explorer filter to see the batch again. i thought that this was a filters problem, but it wasnt..both times the filters are set to the exact same settings.
has anyone encountered this problem?

thank you so much in advance,


Phil

[tmanery]

philvan, on 18 April 2011 - 11:12 AM, said:

Hey all,

I'm experiencing a weird problem with Profile. Basically, our workflow is set up so that when a client file is properly inputted, it gets reviewed, where the reviewer looks over the file and saves the file as 'ready to print'. after a batch is created (ie 20-30 on client explorer), the reviewer logs off and another person logs on to print the files/efile it etc. now our problem is, the batch that was already built often doesnt show up! the printing person would have to go into each file again, and re-save them again (just a simple file, save as, no setting had to be changed! but still, for large batches, this is a bottleneck to the workflow) in order for the client explorer filter to see the batch again. i thought that this was a filters problem, but it wasnt..both times the filters are set to the exact same settings.
has anyone encountered this problem?

thank you so much in advance,


Phil

[tmanery]

The reviewer and the administration staff printing are not setup on the same database. The database tracks the files and their status.
That is why when they go into the client explorer it is not seeing the updates or files at all.
On each machine go into the Options, then database and make sure they access the same "shared' database off the server. All your problems will then go away.
I also recommend you re-index your database to make sure it is up to date.

[philvan]

Thanks for the quick reply, I will implement the changes and see how it goes, will report back :) thank you again

Phil

[philvan]

ok. now that i've familiarized myself with the database, understanding the way it works on a shared network the problems have gone away :) thank you

[philvan]

ok so the problem actually didnt go away.

We're making a client list right now so that we can cross- check our 'efile accepted' list with it to ensure we've left noone behind - as a safety measure.
we've done this by printing every acknowledgement report (for the efile accepted list)...and using client explorer's report function, with all options in the filters function ticked on, to create a client list of all 2010 returns that has been carried forward.
the problem is, now as i'm going through our 'efile accepted' list, i'm encountering names that are not on that client explorer report!
i can remedy this once again by opening the problem file, saving it (without even changing any settings). once i do that, i can 're-filter' client explorer and the file would now appear on the client explorer list.
the problem seems like client explorer still isnt tracking the file status correctly.
right now the only solution i know is to open every file in the system and manually resaving them to make sure they're all included in the client explorer report.
however, that would take a very long time lol.
is there a way for me to command client explorer to 'refresh' its knowledge on the files statuses???

Thank you very much in advance!

[tmanery]

As I stated before you need to re-index your data base, and then all the files will show up properly.

[philvan]

I'm sorry, I did the 'shared' database solution that you gave, and sicne the problem appeared to go away, or so i thoought, i didn't do the second part of your suggestion. After some fiddling around I managed to reindex our database and now it is indeed all fixed. Thank you again :)

[Tim Parris]

As a former manager of a large tax preparation office with 8 staff, I would generally reindex the database twice a week before anyone got in. People always commented that the system seemed faster those mornings.