Hello Together,

our customer needs a project entity. He also wants to define Projects under
the main project like a tree-structure. If he creates an activity in a
project that has a parent project he wants that activity to show up in the
parent project. He wants something similiar to accounts and subaccounts for
the projects.

My first thought was to rename the opportunity entity to projects because
the customer needs to close the projects and wants to define relationships
to accounts in the project. But i can't create parental relationships
between a system entity and itself. Another thing is that the customer also
wants to define relationships to accounts for the projects that have parent
projects.

Any Idea how to do that with CRM?

Hi Mark,
I think, still the better option is to use Opportunity entity as Project. If
you create custom entity than you will not be able to see the activities of
child entity in parent entity. This is only possible in built in entities.
Even in case of custom entities, you cannot have parent child relationship
directly. Check out following blog "Overcoming relationship restrictions in
Microsoft CRM v3.0"
http://andrewn23.blogspot.com/
This will explain you how to overcome relationships limitation.

Another option is to use existing relationship entity.

--
PLEASE do click on Yes or No button if this post was helpful or not for our
feedback.

uMar Khan
Email for direct contact: imumar at gmail dot com


"Mark Spoonman" wrote:

Hi uMar,

i already read that post for overcoming relationship restrictions but can i
have activities shown up in parent opportunities with that solution?



"uMar Khan" <imumar@gmail.com> schrieb im Newsbeitrag
newsC4C15F4-264B-4C1F-B299-67C640754F7B@microsoft.com...

Nope, that is not possible. The other option is to develop aspx form using
CRM SDK and show child entity's activites. You may show this aspx form in
IFrame in some tab or make a link in left navigation of opportunities.

--
PLEASE do click on Yes or No button if this post was helpful or not for our
feedback.

uMar Khan
Email for direct contact: imumar at gmail dot com


"Mark Spoonman" wrote:

Because it is hard to convey over a newsgroup exactly what you want. This may
help.

We had an issue where we have set up an Asset Management system.
Firstly create entities renaming has only lead us into trouble and will be a
pain to upgrade.
If the number of levels of a project is fixed then create entities for each
level and link them, then create relationships with any entity.

For instance we have a Main Asset Group, Asset and Activity Code, that the
user selects on the Order and Invoice entities. By selecting the Asset and
the activity, the classifications are handled by the Main Asset form which
has the group on it.

So if you have fixed number of Project Levels you could design it to use it.
ie Main Project 001
Sub Project Level1 001
Project number 1000
Activity code Lab -Labour

Give the lowest level project an ID of 001-001-1000 and have one lookup on
the form for project code and use the Main Project setup form for the
Grouping.

Is only a suggestion

--
Warren Shrimpton
Leading Solutions


"Mark Spoonman" wrote: