I am looking for the capability to approve a Purchase Order in Dynamics GP using eConnect. I do not see this capability when reviewing the eConnect Programmer's Guide, but I would like someone with more experience to verify that I am not missing it, please.
If it matters, please realize I also have no experience in approving POs through the GP application so I am not certain how this operates on its own. I have a vague recollection that this approval happens in a workflow whose functionality was added somewhat recently in GP's history. So perhaps a second question, is this approval functionality part of the stock Dynamics GP install or no?
Thanks
You can add purchase order approval functionality to Dynamics GP by enabling the option in the Purchase Order Enhancements Setup window.
Microsoft Dynamics GP menu -> Tools -> Setup -> Purchasing -> Purchase Order Enhancements
Refer to the manual for Purchase Order Enhancements from your installation media or download it directly from Microsoft.
In a nutshell, it allows you to set up security around approvals with limits on dollar amounts and restrictions by purchase order number, vendor, or created by.
There is no eConnect integration to approve purchase orders, but you may create your own process by extending eConnect with custom SQL logic. If you are unfamiliar with the database schema in Dynamics GP you may want to reach out to a Dynamics GP Partner for assistance with that development. I wouldn't recommend directly modifying data in the Dynamics GP database without a complete understanding of the impact.
With that said, this is a fairly simple customization for someone with a good understanding and experience with the purchase order module in Dynamics GP.
Go to Microsoft Dynamics GP menu -> Tools -> Setup -> Purchasing -> Purchase Order Enhancements and activate the approval setup.
Once the user having PURCHASING role he can able to approve any PO.
Related
I would like to be able to supply external users (customers, potential leads, suppliers) across organisations and internal users inside my organisation with documents.
The documents should be organisable per user individually. E.g. Customer A should be able too see documents for the product he bought, not more and not less documents.
No further functionality is currently needed besides that.
Is SharePoint the right tool for that job?
If not what other tools can you recommend from your experience?
I see you tagged SharePoint 2019, I'd advise against using on-prem SharePoint for Sharing documents externally. It is possible, but to do it securely is complex and expensive.
O365 on the other hand is pretty simple and the security is already implemented for you. You can determine the level of access that your external users have and you can extend that by using additional tools provided by Microsoft Information Protection.
You can secure access by forcing guests to login or simply have anonymous links. To add to that you can automate your publishing processes using Power Automate, the O365 workflow.
Take out a trial subscription and make sure it meets all your requirements first.
I am creating organization architecture in dynamics CRM.
I have one question regarding - Site vs Sales Territory
or BU vs Site
When exactly we should create Site, Sales Territory or BU ?
Or we can say what are the limitations of them ?
I have gone through many forums and websites but not able to find any good document on this.
Any online book which I can read to understand this difference ?
Any help on this will be greatly appreciated.
Thank you,
Mittal.
Those are all quite different things used for different purposes. You may find you will need all three or just a couple depending on what you are trying to do. E.g. If you are not doing any sales you wont need sales territories, if you want to model a security model where only some users can see some data you will want business units.
I would suggest digging into each area in more detail (scheduling, sales, security) as described below to make that decision.
Sites are part of the scheduling engine.
In Microsoft Dynamics CRM 2011, a site entity represents a location or
branch office where an organization does business. Many Microsoft
Dynamics CRM customers have multiple sites. Sites enable resources,
services, and appointments to be defined at a particular location with
an associated time zone. Location, correct selection of resources, and
time zone are important elements in the scheduling of service
appointments when multiple locations of doing business are involved.
You can use sites to limit what resources, such as users and
equipment, can be scheduled for a specific service activity.
When you search for an available service activity resource calendar
time slot, to avoid making an appointment in the wrong location, the
scheduler must be able to select the site or delivery location as a
constraint to the search. For example, a customer may ask for an
appointment at the Seattle office. To support this, there must be a
site named Seattle and there must be required resources assigned to
the service type to be performed. When generating appointment
proposals, Microsoft Dynamics CRM 2011 must be able to avoid proposing
appointments with resources that cannot physically be together to
provide the service. The site entity serves this purpose. Sites
provide for the grouping of resources, such as users and
facility/equipment, services, and appointments, according to a
location with an associated time zone and locale.
Sales Territories are part of the sales process.
Microsoft Dynamics CRM 2011 uses the fiscal calendar entities and the
territory entity to track sales information for a salesperson. A
salesperson is a user in Microsoft Dynamics CRM who has to meet sales
objectives, such as sales quotas. A territory is a geographical area
that is assigned to a salesperson.
Business Units are part of the security model.
An organization in Microsoft Dynamics CRM, such as a holding company
or a corporation, is made up of business units. A business unit is a
unit of the top-level organization. Business units can be parents of
other business units (child business units). The first business unit
created for an organization is called the root business unit.
A business unit can own records as defined in the ownership type in
the metadata definition for an entity.
I have integrated our SharePoint site and our Dynamics CRM 2011 system so that we can upload documents from CRM. But i had a thought that through security in CRM users can only see records relevant to them, but if they just went to the SharePoint site they'll be able to see documents related to any record even if they couldn't see it in CRM.
So i was wondering if its possible in some way to 'sync' the security from CRM into SharePoint so that users can't see what they're not meant to in either system.
Thanks
It is possible out-of-the-box. There is a commercial CB Replicator solution that solves exactly this problem. It performs complex mapping of CRM security model into SharePoint groups and and folder level permissions.
Shortly described it deploys tiny plugin into CRM that collects all the events that could require change of permissions. There is a standalone service that gets these events and write proper permissions into SharePoint as item level permissions on referenced folders by sharepointdocumentlocation entity.
It support various action in CRM that lead into permissions change, e.g.s security roles, business unit hierarchy, privilege depths, team membership, access team, access team templates, sharing.
Unfortunately this isn't possible out of the box. SharePoint's security model is usually based on AD groups, whilst CRM uses in-app security roles applied per user.
To keep these in sync would require some custom development on the server side, that is if it's possible at all.
I have couple of questions related to the usage of Dynamics CRM:
Can it be used like a shopping website?
If I am using it like a Shopping website, will I have to buy a license for every registered user on my website?
Or do you think Dynamics CRM is not made to behave like a shopping website?
1) Absolutely, with some development, Microsoft CRM can be used as the database for your shopping website. You can use the built-in product catalog and price lists for your sales. Microsoft CRM has entities built into it for lead -> opportunity -> quote -> order -> invoice and you can repurpose any or all of these to work as you need them.
2) Typically the users of your shopping website will coincide with CRM contacts, which is great because you don't need user licenses for them. You will have to license each end user of the system but this is limited to employees of your business. In some scenarios you may need to purchase one external connector license which licenses you to expose data through a web site or other medium - see this blog for more details http://blogs.msdn.com/b/mscrmfreak/archive/2007/06/01/repeat-external-connector-license.aspx. You will need to develop the website shopping site front end and integrate it with Microsoft CRM using the Dynamics CRM SDK.
3) Building portals to Microsoft CRM is actually a very common request. A shopping website is a type of portal, another type would be a customer self service website. Both can utilize the Microsoft CRM database to get 60% of the way, and then integrate with the website.
While you could use Microsoft Dynamics CRM to build a shopping website, I wouldn't recommend it. A CRM and a framework for ecommerce are two different beasts. Look for a product that is specifically created for a shopping website, rather than attempting to manipulate Dynamics CRM.
I have integrated our application with Microsoft Dynamic GP. If any of the user in Dynamics GP has updated any customer/vendor/other, then we need to update those data in our application.
How can we achieve this?
There are many ways you could do this, but the three that immediately come to mind are:
Add your own triggers to the Dynamics GP tables that you're interested in. Make sure you test them well (so that they don't break GP), and that you script them out, since upgrades to GP might result in (or require) their removal and subsequent re-deployment.
Use Microsoft eConnect for Dynamics GP (http://msdn.microsoft.com/en-us/library/aa973830.aspx), and leverage its Transaction Requester Service (http://msdn.microsoft.com/en-us/library/aa973839.aspx). [I'm a Microsoft partner, and I consult on these products, but I'm not otherwise affiliated with Microsoft.]
Use a third-party app like SmartConnect from eOne Business Solution (http://www.eonesolutions.com.au/content.aspx?page=SmartConnect), which leverages the eConnect runtime, and which provides a toolset that simplifies the creation and management of integrations with Dynamics GP, including real-time integrations. [I'm not affiliated with eOne - just a fan of SmartConnect.]