Blogs

Users cannot see renamed form navigation pane group headings

If you have customized the Group Names (i.e. 'Common', 'Sales', 'Service', 'Marketing', 'processes') located in the form navigation pane of Microsoft Dynamics CRM, you need to assign the appropriate permissions to users so they can actually see these changes. The privilege inside of the security role that needs to be turned on is called 'ISV Extensions' on the Customization tab. This privilege is already given by default to management roles. If a user does not have this privilege they will not be able to see any changes to the headers-- rather it will look like no change has been made at all.

Watermark SSRS Report - How To

Recently when I was creating an SSRS report and was having a difficult time inserting a watermark. Unlike Microsoft Word, there is no button called "watermark" where one can be easily inserted. I could also not find a way to have a text box with an adjusted transparency.

Instead I came upon a very helpful blog that describes how to add a watermark into your report using a custom image. It's as easy as opening Microsoft Word and either creating your own text or using the Watermark button, saving as a .png file, then adding the image into your report. Please refer to the following link for the article.

http://www.heysup.net/ssrs-tutorials/ssrs-how-to-watermark-your-report-w...

Personalize your CRM ADFS Sign-in page

Njevity and our partners wanted to brand the sign in page for our Microsoft CRM ADFS logon page. To do this we had to add a logo file and edit a couple of code and configuration files.

On our ADFS servers we did the following:
1. Copied a our logo graphic file to c:\inetpub\adfs\ls (the root directory of the ADFS web page)
2. Made a backup copy of the web.config file in the same directory
3. Opened web.config with notepad
4. Found and un-commented the
<add key="logo" value="logo.png" />
key
5. Edited the key to point to our logo file.
6. Saved and closed the web.config file.
7. Made a backup copy of c:\inetpub\adfs\ls\MasterPages\MasterPage.master.cs
8. Edited MasterPage.master.cs
9. Change the line
Page.TitleLabel.Test = PageTitle ;
to
Page.TitleLabel.Test = "Sign In to:";
10 Change the line (so the logon page does not display the server name)
STSLabel.Text = FriendlyName;
to
STSLabel.Text = "";
11. Saved and closed the MasterPage.master.cs file.

Grant Permissions for Manufacturing SmartLists

When using Manufacturing in Microsoft Dynamics GP (both GP 2010 and GP 2013), people not assigned to the POWERUSER role are unable to see Manufacturing SmartLists by default - even users who are assigned MFG ADMIN and MFG_INQUIRY roles.

To grant permissions for these, you need to include them with a task. You can assign the permissions to whichever task you choose. I choose to assign different SmartLists to their matching inquiry task (INQ_MFG_XXX), in case custom roles are added for which there should be limited manufacturing permissions.

To add SmartLists to a Security Task:

1. Open the Security Task Setup window (Administration >> Setup >> Security >> Security Tasks)
2. Choose the Task ID for which you would like to add SmartList permissions
3. Select Product: Smartlist, Type: SmartList Object, Series: SmartList Objects
4. Check the boxes next to the SmartLists you would like to include
5. Click Save

The tasks to which I assign Manufacturing SmartLists:

INQ_MFG_BOM*
-- Bill of Materials

INQ_MFG_MO*
-- Manufacturing Orders
-- Picklists
-- Recorded Outsourcing Shipments
-- Sales Documents Not Linked to Manufacturing
-- SO/MO Link
-- Suggested Outsourcing Purchase Orders
-- Suggested Outsourcing Shipments

INQ_MFG_WIP*
-- Work in Process

GP Manufacturing Accounting Flow: Component Transactions and MO Receipts

In GP Manufacturing, the accounting flow for inventory transactions involved in a Manufacturing Order can be tricky, because they don't all follow the same logic. Below is a summary of the accounting flow for some of the basic inventory transactions that take place during the Manufacturing process.

Component Transaction Entry (Issue)
Issues raw materials to production/WIP:
-- Credits (decreases) the Inventory account
-- Debits (increases) the WIP account
 
To determine which inventory account to use, GP checks the Inventory account assigned to the Raw Material item.
-- If this is present, it will use the account
-- If it is blank, it will use the default posting inventory account
 
To determine which WIP account to use, GP checks the WIP account assigned to the Finished Good item that is being produced:
-- If the WIP account is present, it will use that account
-- If the WIP account is left blank, it will use the account assigned as the Inventory Offset account for the Raw Material item
 
IMPORTANT NOTE: If you perform a REVERSE ISSUE, which brings Raw Materials from WIP back into inventory, GP will put the Raw Materials cost out of WIP and back into inventory. However, if the WIP account of the Finished Good item is blank, it does not use the Inventory Offset account from the Raw Material item. Instead, it allows the transaction to post, leaving the WIP account blank. The resulting GL does not balance so it does not post, it has to be completed and posted manually.
 
MO Receipt
Completes production, consumes Raw Materials from WIP and issues Finished Goods to inventory:
-- Credits (decreases) the WIP account
-- Debits (increases) the Inventory account
 
To determine which inventory account to use, GP checks the Inventory account assigned to the Finished Good item.
-- If this is present, it will use the account
-- If it is blank, it will use the default posting inventory account
 
To determine which WIP account to use, GP checks the WIP account assigned to the Finished Good item that is being produced:
-- If the WIP account is present, it will use that account
-- If the WIP account is left blank, it will post the transaction without a WIP account and not give an error to the person posting the transaction. When it posts:
     - Inventory quantities are increased
     - An incomplete GL transaction is created, but does not post all the way through because it does not balance
     - The GL transaction needs to be completed and posted manually

 

Syndicate content