PLEASE return to the option of Show Details and Fix It. The 2020 program option is only yes or no. The problem is that all our tax files are saved on a network file. When yes is selected all those files are reconciled. Result is a HomeBase View that has all of our company's tax files. In prior years I would choose to Fix It which allowed me to select specific files. My HomeBase View would then only show the 100 tax files I work on instead of the entire 5,000 tax files for the company. Staff also would have in their HomeBase View the files they only worked on instead of the entire company's files.
The challenge is that the ability to selectively work on a subset of files shared on a network drive sounds a lot like what our network product is for. This wasn't explicitly removed for any reason... it's just that when we had to reimplement this feature due to our database migration we only solved for the expected scenario of repairing a database.
That being said, I am looking into alternative ways of accomplishing this and we are very actively discussing the requests.
As one alternate suggestion.. you could import every file, and then rely on homebase filters to limit what people have to work with. For example, you could filter by Preparer, FIle Name or Client Status, for example. I can appreciate though that wouldn't work if who works on what is based on something that doesn't show up in a column.
@OrlandoIf we place a file in the folder where the data files are to reside we cannot find them when a database reconciliation takes place. We have preparers that work from home so they keep all files on their laptop. We then put them on the server and work on them. We can't see them.
@Ernie Are you including the .cache file when you do so? That's new this year. So for example, if you have a file named john_smith.20i, there will be a corresponding john_smith.20i.cache file. You have to copy both, from what I've been told, if you are manually moving them around and using database repair.
Alternatively, if you have just the john_smith.20i file, you can open it and then save and the file will be added to homebase with a new .cache file. Of course, that'd be painful if you have more than 1.
Feedback is welcome.. we're really trying to understand if these changes are just not sufficiently communicated, or if the expectations aren't matching the reality.
@Orlando So here is what I tried. I created a file on a laptop. I transferred the file and the 20i.cache file to the PC that does the printing. I can then see the files and homebase does find them. I guess I didn't understand that we needed to transfer the 20i.cache file along with the data file. That is different.
I sync laptop computer with desktop computer through Google Drive, using Backup & Sync. I don't want my software deciding for me which file to keep and which to discard. Sometimes I deliberately create a test file from an existing client and decide from my desktop computer how to handle. Last year we could decide and act on :
files not currently in HomeBase
records found for non-existent files
HomeBase records needing updating
possible duplicates
Now the program just tells me it "fixed it" What the hell did it "fix" ?????
Some times I may not want the software to put a file in HomeBase ! When it says "fixed" - did it ? did it not? did it overwrite something I didn't want overwritten?
Please allow "us" the customer who pays for the product decide .
Theres a thread somewhere addressing this, it was a couple weeks ago, I dont want to go digging, sorry.
They made changes to HB...... seems like they want people to pay for a network license to use a network....but I dont really understand how all that works.
The team made changes to HomeBase and HomeBase Maintenance out of necessity.Both depend on the underlying database, which had to be swapped out for the long term health of ProSeries. As part of this effort the team focused on re-implementing HBM to solve for database irregularities, and did not identify the various additional use cases and preferences for control discussed in this thread.
The more people vote on this, the better to allow for prioritization over other requests.
Yes I read the article and it stated it would let you know if
There are two or more database records with the same social security number or employer identification number, which indicates that there are duplicate client files
But it doesn't tell what tune-up does when it encounters this condition - just that it'll fix it for you ?
I don't disagree - I would prefer more control and visibility too.
I'm just looking to accomplish two things:
* Explore viability of work arounds and alternatives in the immediate term
* Gather data/feedback to help with prioritization for our next update and beyond
In your case, can you describe what you wanted to accomplish in TY19 and what you did to accomplish it? I know you mentioned creating a test file from an existing file - do you mean you copied it in File Explorer in order to experiment with data? If so, what did you use HBM for afterwards? For example, to decide to replace the original if you were happy with the outcome?
Please forgive the questions.. again I'm just looking to build the case for addressing this, while offering possible alternatives with TY20.
