It’s nice to be able to drilldown in FRx instead of going to the GL. Saves a few steps. I’m not going to show you what the finished product looks like because I’m in a demo database and the transactions look pretty tacky. But suffice to say that there’s probably a lot more to drilldown than you ever dreamed. [click to continue…]
{ 7 comments }
Jun.
21
2010
For the most part, you should use the Format Code PI in the row format instead of the PB code. Why? Well, PB doesn’t actually stand for Page Break. It means “give me a new page for a balance sheet, and skip all those messy P&L accounts along with their column headings”.
So when you generate your report, if you’re missing accounts and activity after what you think is a Page Break, PB is probably the culprit. It looks like FRx is buggy, but it’s designed to work this way. Switch it to PI and you should be good to go. [click to continue…]
{ 1 comment }
And you might be wondering what pieces of FRx will get lost in the shuffle. This is a laundry list that I got a couple of years ago from a Microsoft contact. Along with a few of my own comments!
Note: If you don’t use Microsoft Dynamics (either GP, AX, SL, or NAV), you can skip this post. [click to continue…]
{ 5 comments }
Jun.
4
2010
Run them one at a time? Well, most people turn to Chaining in the Output tab. That’s all well and good, but often I like to use Launcher instead. It’s fast and there’s no setup involved.
(Launcher was technically designed to allow non-designer users to run reports. Most folks don’t want the CFO in there fooling around with the designs, right? Give them Launcher and allow them to generate reports all day long without touching the FRx Designer.) [click to continue…]
{ 1 comment }
