Inconsistencies in Access to System Fields (in MooD 16.025)

Completed

Follow

Peter Kristensen

• October 30, 2017 10:23

There are some inconsistencies in how system fields can be accessed, depending on the used type of control. I understand that inconsistencies can creep in as the product is being developed, and there is nothing critical in these inconsistencies, but it is a huge annoyance when using BA, and it makes it unnecessary difficult teaching BA to others, so it would be good to get them fixed.

I have mapped out the inconsistencies here:

Here are the major points:

• Id, Created Date, Modified Date, and Element Type cannot be accessed from a Label
• Created Date, Modified Date, and Element Type cannot be accessed from Aggregation Matrix and Smart Column facts
• Name/Element Name can be updated from a Text Editor but not a Field Editor
• Name/Element Name cannot be updated from a Button
• It seems unnecessary complex to have Element Name when Name (the string field) could just be used instead

Here it is in terms of the template:

As a solution builder, I want to be able to access system fields in a consistent manor from all relevant controls, so that I can build simpler solutions and a do it in a more stressless manor.

Benefits are increased efficiency, happier BA users, and easier to learn using BA.

Priority is medium.

5

• Official comment

  

  Iva Sharp

  • November 02, 2017 16:30

  Hi Peter,

  Thank you for the request, it has been logged with the Product Owner.

  We'll get back to you in due course,

  Iva

   

  Comment actions Permalink
• 

  Giles Middleton

  • October 31, 2017 17:17

  Just to clarify, when you say Label, do you mean 

  "When I place a label action panel on a model, and tie it to a subject, I want to be able to edit the Set From, to choose the ID, Name, Created date, Modified date, element name, element type."

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • October 31, 2017 23:06

  Yes, that is it exactly.

  1

  Comment actions Permalink
• 

  Peter Kristensen

  • November 14, 2017 20:20

  Found a case where the system fields are not accessible in the query builder:

  

  2

  Comment actions Permalink
• 

  Iva Sharp

  • December 06, 2017 17:46

  Hi Peter, 

  Would you be able to give an Acceptance Criteria for this story? 

  Thanks,

  Iva. 

   

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • December 07, 2017 00:03

  Sure:

  • The five system fields - Id, Name, Created, Modified, Type - must be accessable everywhere* where fields can be used.
  • The system fields must have consistent names and be consistently selectale. This is especially relevant for Name, which now has two different names and can be selected in three different ways.
  • "The subject element" may still be available because it has a different purpose.

  * "Everywhere" may need to be defined, but I am not sure I have the full list. At least it includes:

  • "Select Source for Information" pop-up selector
  • Query builder
  • Aggregation matrix and smart column facts and dimensions

   

  Regards,

  Peter

  0

  Comment actions Permalink
• 

  Iva Sharp

  • January 25, 2018 11:11

  Hi Peter,

  We have discussed your feature request during our MooD Roadmap meeting, and have decided to implement your story into MooD.

  The feature request is currently in the development backlog, and we look forard to notifying you when the feature will next be available.

  Best regards from the MooD team, Iva.

   

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • April 21, 2018 15:23

  I haven't re-tested everything, but nothing seems to have changed in MooD 16 build 32.

  0

  Comment actions Permalink
• 

  Kevin Stebbing

  • July 11, 2018 14:32

  We've been looking in to this.  There are a number of different cases.  Some are clearly inconsistencies which can be cleaned up.  Name should be made available everywhere and Element Name removed. Labels should have the same fields available as Info Panels.  For facts in Aggregation Matrices and Smart Columns the value is less obvious.

   

  Could you give a priority order of which cases are most important?

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • July 11, 2018 19:19

  Hi Kevin,

  My priority is absolutely on consistency.

  I try to keep a model in my head of MooD's technical capabilities, so I can quickly answer customer questions about what is possible and not. Because MooD is a complex tool - which make it do great things - I can not possible keep all exceptions and inconsistencies in my head. E.g. I will think that I can get the element name in a particular case, and I will tell the customer that this is possible. Then afterwards I will discover in this particular case it is not possible.

  So, I want to get rid of these inconsistencies to help me be a better consultant and also to make it easier for new MooDlers to learn.

  I know this isn't that answer you were looking for, but it is important for to emphasise that the consistency is the priority, and not were it is most important for me to have e.g. element name available.

   

  Regards,

  Peter

  0

  Comment actions Permalink
• 

  Hugh Emery

  • July 12, 2018 10:24

  Hey Peter, 

  As always, thanks for the feedback. We share the same goal of improving product consistency. In this case however, the story is large and we are trying to break it down into component parts. They key thing we are looking for is what order should we approach this problem in. From your perspective, could you detail some bullet points of what are the most painful blockers caused by this consistency issue? Where has this caused the most pain?

  Kind Regards,

  Hugh

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • July 17, 2018 10:23

  Here is my priority based on the problems I most often encounter:

  1. Consistent access to Name/Element Name
  2. Consistent access to Created and Modified Date
  3. Consistent access to Subject Element
  4. Consistent access to Element Type

   

  0

  Comment actions Permalink
• 

  Kevin Stebbing

  • September 20, 2018 09:44

  We've completed some work on this:

  • The custom Element Name navigators have been replaced by system field Name navigators.
  • Created Date and Modified Date are now available in Facts for Aggregations and Smart Columns.

   

  1

  Comment actions Permalink

Please sign in to leave a comment.