search

Ardalyst / Celedon-Autonumber-RTM

Celedon Autonumber Solution for Dynamics CRM
http://www.celedonpartners.com
MIT License
19 stars 24 forks source link

Would like to access a grandparent value for the prefix or the suffix. #1

Open StephenDKing opened 7 years ago

StephenDKing commented 7 years ago

Not really an "Issue" more like a feature request, I need to have a prefix on an entity which uses a value from a grandparent entity.

Here is how the hierarchy works: Proposal -> Opportunity (lookup) -> Department (lookup) [new_Suffix] {opportunity.new_department.new_suffix|00}{createdon:yy}-

Let me know your thoughts. -Stephen

tsharp commented 7 years ago

Just for clarification: Opportunity is a lookup on a proposal, and you need to look at a the department field suffix that is specified on the opportunity?

wedge905 commented 7 years ago

This can be done with the existing functionality. You would just have to add a calculated or autonumber field on Opportunity that gets the value from the grandparent. That way there's no need to pull directly from the grandparent to the child.

Some thoughts on this request:

On the other hand... OOB calculated fields only supports immediate parent. So a project like this could differentiate itself by being better than OOB.

Just my $.02

StephenDKing commented 7 years ago

That is correct.

On Fri, Jul 14, 2017 at 12:57 PM, Travis Sharp notifications@github.com wrote:

Just for clarification: Opportunity is a lookup on a proposal, and you need to look at a the department field suffix that is specified on the opportunity.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/BESDev/Celedon-Autonumber-RTM/issues/1#issuecomment-315425112, or mute the thread https://github.com/notifications/unsubscribe-auth/ADUICQW1HPaZMxeOF3bM_UaVoMKkK4u2ks5sN6vxgaJpZM4MlWsW .

-- "Every day is a journey, and the journey itself is home." -- Matsuo Basho

StephenDKing commented 7 years ago

Thank you for the response, I had planned on attempting this myself and am still willing to; I had tried earlier but as others had pointed out there was an issue with it and i needed something "right then" so i moved on to write my own.

Since i can now open the project. i can take a crack at it. I'll be more than happy to contribute... or at least try to.

Any other thoughts?

On Fri, Jul 14, 2017 at 3:03 PM, Matt Barnes notifications@github.com wrote:

This can be done with the existing functionality. You would just have to add a calculated or autonumber field on Opportunity that gets the value from the grandparent. That way there's no need to pull directly from the grandparent to the child.

Some thoughts on this request:

  • When this was initially built, it intentionally only supported immediate parent lookups. Partly for simplicity, and also because it follows precedent (OOB calculated fields only support parent as well).
  • Once you get to grandparent, it could introduce performance issues, because multiple retrieve calls will be needed to get the final value
  • If grandparent is supported, where should the line be drawn? Why not great-grandparent or beyond?
  • An issue with a grandparent lookup, is that it introduces the possibility of a circular reference. Think of Account/Contact: You can have Parent Account on Contact, and you can have Primary Contact on Account, and in some instances that would be an infinite loop.

On the other hand... OOB calculated fields only supports immediate parent. So a project like this could differentiate itself by being better than OOB.

Just my $.02

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/BESDev/Celedon-Autonumber-RTM/issues/1#issuecomment-315454205, or mute the thread https://github.com/notifications/unsubscribe-auth/ADUICao4CSXMyiNlawcGxUX4QAEoE3ofks5sN8mNgaJpZM4MlWsW .

-- "Every day is a journey, and the journey itself is home." -- Matsuo Basho