Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
RTC Control-Addin, variable change of backcolor, Font, Size
Jan79
Member Posts: 7
Hello!
I built the msdn-example for control-addins and i got now the question how it is possible to pass data from Nav to Addin without using SourceExpr?
My example:
Customer Card, Field "Name".
I want the Backcolor/Bold changed like in the MSDN-Control-Addin example, but i want to parametrize it, so it is general Addin and not a "constant" Addin "FieldLightBlueBold", "FieldRed", "FieldGreenBoldItalic" for evry possible combination.
I checked different blogs and msdn and they always use SourceExpr with xml but that doesn't work with a "real" field.
Any help is appreciated
Thanks in advance!
Cheers,
Jan
I built the msdn-example for control-addins and i got now the question how it is possible to pass data from Nav to Addin without using SourceExpr?
My example:
Customer Card, Field "Name".
I want the Backcolor/Bold changed like in the MSDN-Control-Addin example, but i want to parametrize it, so it is general Addin and not a "constant" Addin "FieldLightBlueBold", "FieldRed", "FieldGreenBoldItalic" for evry possible combination.
I checked different blogs and msdn and they always use SourceExpr with xml but that doesn't work with a "real" field.
Any help is appreciated
Thanks in advance!
Cheers,
Jan
0
Comments
It is a limitation in the Add-Ins that they support binding to a single value using source expressions. (Of course on the Add-In Site interface it gets additional properties like Enabled, Editable, Style, Caption etc that can be used by the Add-In to influence rendering.)
The root cause of the issue is the following:
While having a "PinkField" Add-In is a nice easy to implement HelloWorld type sample that can easily be used to demonstrate the use of an Control Add-In it is not the intended use of Add-Ins. The primary use case we had in mind at designing this feature is not to use Add-Ins to substitute elements of the UI with custom controls, that is applied to lots of fields with ease. The goal is to provide possibility to advanced visualisation like in case of the TreeMap sample: You have it in just a few place in your NAV application but it provides bigger increase in end user interaction value. Another possible scenario is when you have some client side integration component (like a Bar-Code-Reader) and you want to embedd its custom interface into the NAV user interface instead of displaying separately.
In such cases when the Add-In appears just on a few page then using a single source expression with all the required parameter channeled into an XML description is a small limitation. (I guess mostly performance issues might arise)
In your specific example as a workaround you can try to use the Style property with its 5 possible value. Or as a nastier one make the Add-In display the Caption as well and then use that to channel metainformation. Finally you might move the logic determining the display style into the AddIn. (Like create an add-in that if its value is a negative number is red, and if positive it is green.)
Whichever option you choose in you Add-In implementation make sure you just send such information to the Add-In you wouldnt be afraid to show your end user directly. It is in his box after all.
I hope it makes sense.
Gabor Pesti
“This posting is provided "AS IS" with no warranties, and confers no rights.”
Software Developer Engineer in Test
MSFT
Dynamics NAV