While I was restarting my website this month I came across a funny fact: there are still sites out there that link to my XP Common Controls Project (XPCC) back from 2004.
The longest and hardest fought over sessions in a Vision implementation are always project numbering and project structures. While project numbering is usually defined by a legacy application or legacy filing system (and it’s less of an issue as most people think) I came across some misconceptions on Vision’s Work Breakdown Structures (WBS) and how to use them.
Did your finance department ever approach you to create them that one specific report that’s missing? Did you ever wonder if you could write a report that would take advantage of Deltek Vision’s ® reporting capabilities and allow you to create selections, set up your own grouping, show and hide columns and create your own favourites? Or did you ever wanted to create invoices with a bit more bling than the plain standard ones? Then
I just came across a System.Threading.Timer issue and thought I might share it with the community: As part of a background task that pulls data out of Vision and sends it to a 3rd party I implemented a background task into a ASP.net Web Service using the System.Threading.Timer and TimerCallback.
The most used and by far the easiest way of customizing Deltek Vision is the User Defined Controls feature. This allows you to add new fields and grids to any existing info center (like projects, employees, vendors, etc..) or even create your own new info centers from scratch. Custom fields support all the data types you know from standard Vision like numbers, characters, dates, memo-fields, etc… but you can also select any of the info
Sign up to get the latest updates on new content from this site