So I just discovered String templates and they are amazing.
Is there a resource where I can find what each SAP release brings to ABAP ?
Not strictly an SO question, but it will make all ABAP developers better if they can study what is new in the releases.
Transaction ABAPDOCU, then navigate to ABAP Keyword Documentation --> ABAP - Release-Specific Changes:
Related
I am developing a Word add-in with Office.js that utilizes ContentControl.insertText. According to the documentation, this method is provided by WordApi requirement set 1.1, which is supported in Office Online. Furthermore, the documentation for ContentControls lists Office Online as being supported and does not mention any exceptions when it comes to using that particular method.
That said, when I run the add-in in native Word 2016, everything works fine, but when I run it in the Word Online environment, it fails with the following exception:
code:"NotAllowed"
errorLocation:"ContentControl.insertText"
message:"The action isn’t supported in Word Online. Check the OfficeExtension.Error.debugInfo for more information."
For reference, I am using it like so:
control.insertText(heading.Text, 'Replace');
I also tried running the example provided in the documentation, with the same results: it works in Word 2016, but fails with the above exception in Word Online.
Has anyone been able to successfully insert text into a ContentControl in the Office Online environment? If not, are there plans for this functionality to be supported?
Any input or clarification would be most appreciated! Thanks!
I'm an engineer from MS. There are some cases which contentControl.insertText is not allowed.
I think the cause of your case is that there is more than one paragraphs in the heading.text and you try to insert heading.text into a inline content control.
The inline content control means that the content control just some part of a paragraph.
In order to make sure the root cause of your scenario, could you share me the doc and the script code.
I can't find a resource that clarifies the programming differences between Polaris and Orion versions. I've been googling for a few days now.
Probably you already read this article written by Jukka Niiranen
The Next Dynamics CRM User Experience: Orion
I think Gemini release will bring (at least) the possibility to use Xrm javascript with the new forms (actually is really a shame to don't be able to pre-fill a field or to do some show/hide logic) and provide the xml definition that will replace the ribbon.
I'm not sure if there is such a document yet. Before we start with Orion, we have to pass Gemini, first. And given the inconsistency between road maps and reality this far, it could as well be that Orion will be known as CRM-2014.
Two questions, hopefully with similar answers.
I'll be releasing a JavaScript package in my solution where the error messages are to be displayed. The problems is that I'll be targeting German, English and French. Possibly, also a fourth language TBD. What would be the nicest way to resolve this?
The label names should definitely be localized. Is there a built-in approach to that in CRM 2011? Like a resource table or something like that?
My current solution for (1) is to keep an extra web resource with the strings and distributing a different file for each language. I may rebuild it and distribute all the languages at once and only use a parameter, possibly settable from the GUI if I create a settings-entity. A bit cumbersome.
My current solution for (2) involves a lot of praying and a divine act of some sort. :)
To determine current CRM user language dynamically from Javascript you can use window.USER_LANGUAGE_CODE (this variable exists on all CRM pages) - for example it will be equal 1033 for English. Than based on that info, you can pick needed string resources from your file.
Also in forms context there are two predefined functions, which return current Organization language code and current User language code: Xrm.Page.context.getOrgLcid() and
Xrm.Page.context.getUserLcid() .
If you are talking about custom entities and fields, you can easily add localized display names for them via your solution. You need to edit customizations.xml file from your unzipped solution. For each attribute there you will find such XML containing display names:
<displaynames>
<displayname description="Created By" languagecode="1033" />
</displaynames>
You can just add new display names for each language you need there.
P.S. If someone interested in different aspects of multilangual support for Dynamics CRM 2011 solutions, I strongly recommend to review this page, also here and here is a very helpful reading.
We are using a site definition and it has 3 feature dependencies that we are struggling to identify:
<ActivationDependency FeatureId="7EDD3C9C-8AC6-4ab5-A209-30B5DC422464" />
<ActivationDependency FeatureId="63FDC6AC-DBB4-4247-B46E-A091AEFC866F" />
<ActivationDependency FeatureId="22A9EF51-737B-4ff2-9346-694633FE4416" />
Can anyone identify what these features or give me an idea as to how to identify them?
I think they are out of the box moss features but they are not installed on the farm currently.
Thanks for any suggestions
22A9EF51-737B-4ff2-9346-694633FE4416 - Publishing Web Feature
The other two GUIDs are not googleable and don't return any results on MSDN. Are they Microsoft features, or could they be 3rd party?
An alternative to Copernic Dekstop search is a tool called Agent Ransack from Mythicsoft. It allows for really good text search in files (in the FEATURES folder of the 12 hive in your case) and it is free. Download it here.
I use Copernic Desktop Search and have indexed a copy of the 12 hive. I frequently use it to search for out of the box and custom features by GUID, just as you are.
As Andrew said, 7EDD3C9C-8AC6-4ab5-A209-30B5DC422464 and
63FDC6AC-DBB4-4247-B46E-A091AEFC866F are not standard features as they were not in the 12 hive. But if you download Copernic (or use a similar search tool) and point it at your solution, you should be able to find the feature definitions pretty quickly.
Is there any way to enforce a template in Bugzilla to guide users fill in bugs descriptions ?
Actually, i'd like to put some markup texts in the bug description field and avoid the creation of custom fields.
I've installed version 3.2rc1.
Indeed, just check ../enter_bug.cgi?format=guided , which forms an example of the template feature. Half the work is already done for you.
The mechansism described under 6.2.5 Particular Templates (under the section called bug/create/create.html.tmpl and bug/create/comment.txt.tmpl) works pretty well for us. Even though you say you don't want to create custom fields, adding some arbitrary HTML is easy enough.