I've been using Smartsheet for about 2.5 years now and gradually discovered how great it is for many tasks within a our small consulting company. While I originally started using Smartsheet for its project scheduling capabilities on large projects, I've ended up using it for much more. During that time I've discovered many features and behaviors of Smartsheet that I didn't see in the early tutorials I watched that ended up being important to me. The items below don't deal with project scheduling since that's not our prime use of Smartsheet today. Many of you are probably more experienced with the ins-and-outs of Smartsheet, but for newbies here are some items that may not be apparent in the tutorials and help pages:
1. Smartsheet has amazing linking capabilities, far beyond what I was used to in Excel. The ability to link literally hundreds of cells between two sheets in one operation enables connections that wouldn't be practical if you had to do them one at a time. There are some limitations, though. You can only link 500 cells at a time and the maximum number of incoming links on a sheet is 5000. That can be extended slightly since it lets you go over 5000 if you are already close to 5000 and you link 300 more, for example.
2. While speaking of Smartsheet limitations here are the main ones: 5000 incoming links; 5000 maximum rows; 200 maximum columns; 200,000 maximum cells; 1MB maximum save size. I've only ever run into the first one.
3. If you remove an incoming link from a cell, the old value stays there. Likewise, if you delete a sheet that is providing incoming links to other sheets, the old values stay there.
4. When you move a row via drag and drop the links all stay as they were. This doesn't work with copy/paste.
5. When you export a sheet to Excel, the formulas are not kept. However, you can call Support and have them set a switch that causes the formulas to be exported also. This works great for exporting normal sheets but it messes things up if you export a report to Excel since some of the cells referenced in formulas typically aren't part of the report.
6. The time it takes to save very large sheets is highly variable depending on what changes have been made. When you insert or remove a row, and immediately save it, it can take up to 45 seconds to save it (that's my worst case). This happens when the sheet is large and there are a lot of complex formulas in the sheet since it has to revise all the formulas that reference cells in rows below the change. Knowing this can help you organize your sheets to minimize the save time if it becomes an issue.
7. The SUMIFS function allows you to do what amounts to database queries on blocks of data linked in from other sheets and then perform calculations on them. For example, in our project timekeeping Smartsheet app I get around 90 records per week where each record includes a project name, the person's name, the function they performed, the hours worked and a brief comment. I gather them using a Smartsheet report that takes data from each employee's timesheet and then copy/paste that information from the report into a master project timesheet. The SUMIFS function lets me organize that virtually random data by project then function and hours each week as well as do billable/non-billable analysis by group and person. I looked at other database products on the market and most of them require the services of an experience software developer to do queries and calculations on data in a database.
8. While I was slow to begin using reports initially, I use them for a variety of items these days. As mentioned above I use them for extracting data from employee project timesheets weekly and to generate formatted tables of data that I then export to Excel for generating weekly charts used by managers and supervisors.
9. I make extensive use of nested IF functions to validate incoming data to make sure it is within expected ranges or that things like project names match our list of active projects. This avoids letting garbage into a sheet that would mess up subsequent calculations and makes finding bad input easier.
10. I find that cell history is great for tracking down when data came into a sheet or who entered it when trying to figure out where/when errors originated.
11. I make extensive use of Conditional Formatting to highlight items that are nearing or out of expected range. For example, a project financial analysis can highlight the net profit in yellow when a project is getting close to breakeven or in red if it starts to lose money. With a list of 40 active projects this makes spotting the ones in trouble much easier.
12. I use Highlight Changes frequently to identify what has happened since the last time I reviewed a sheet before doing final processing on the week's project timesheets, for example. I typically export the weekly project timesheets to Excel for archiving before I recycle them for the next week and want to make sure I have the latest information.
If I've gotten something wrong, I would appreciate your feedback.
