Currently, this is the setup we have:
currentSetup image attached.
With the above setup, we expect the serviceName to be captured as a searchable field in Elastic/Kibana. Instead, the field is appearing inside the message and that makes the field not searchable.
The work around we have is to add the service field as additional Field like below:
workAround image attached.
The above is working and we can search the field in kibana. Do we know why the customField is not working as expected?
Thanks
Related
I have an online form with a custom html. If I make the field mandatory using the UI in the custom record the html for that field is no longer used and is replaced by the default Netsuite one. For example: On my html the label is on top of the field:
Enter Your Name
field goes here
When I make the field mandatory I know get this:
Enter your Name field goes here
No matter what I do with the css I cannot seem to get it to do what the other fields do.
Any ideas on how I can overcome this?
I am trying to use the Contentful web interface to change the name of an entry. Attached is a screenshot. I have searched for 30 minutes for the button that lets me change the title from "untitled" to something else. Alas, it is nowhere to be found on this horrible, horrible interface.
Where is it? Does it even exist?
In Contentful, the entry titles must be handled by a content model field.
In your content model, create a field
Then, tell Contentful to use this field as entry title
Now, you can create a new entry and set the title
I'm currently working on creating a custom display template for people search result page. I copied out of the box Item_Person.html search display template and modified it to display some more fields.
In the out of the box template also there is a managed property called skills but when I using it, its not returning any values associated with the user profile skills property (SPS-Skills).
As you can see its already mapped but Skill value always comes as empty. I want to retrieve and display inside the custom template.
Please help me if you have done something similar.
Check the following steps
Add meta data to ManagedPropertyMapping
2.Then inside the fuction get the value of metadata
<!--#_ var datacreated = $getItemValue(ctx, "Created");_#-->
3.Then palce the variable where you want <h2> _#= datacreated =#_ </h2>
Thats it publish the html hope its work
I have some javascript code attached to the accounts entity. This code sets the requirement level of the primary contact attribute based on the value of a custom option set field showing various account types. This was developed on one server, where it worked, and so the solution was imported into another organisation where it now doesnt work.
It seems to be only on this field as i have changed the code to look at another field and that works fine. The error it gives is that the "Object doesn't support this property or method". Also what is strange is that the field doesn't appear in the list under the entity within the solution despite it being a system field.
The code i'm using is:
Xrm.Page.getAttribute("primarycontactid").setRequiredLevel("required");
Can anyone help me figure out what it's doing?
Thanks
EDIT: Found that the code is actually making the field required despite the error, but it's not displaying the * next to it. Also if I make the field required in it's settings then it does the same thing
I'm having an issue setting the display name for a workflow on feature activation.
What I have got is a workflow that I create with a desired internal name (using SPWorkflowAssociation.CreateListContentTypeAssociation to get an SPWorkflowAssociation object). Once the name is set with that method call, I set the SPWorkflowAssociation.Name to the desired display name after that, add the workflow association to the list, and then call update on the associated list.
The result I see is that the internal name and the display name are both changed (internal name is required to link between the SharePoint list and the Client Side Object Model and we need this internal name as the display name is different for other languages).
Does anyone know how to set this properly in code? It looks like something that should be possible but I'm getting no joy from my investigations.
Thanks!
I got around this by using the description field to store a 'static' name and then later find associations via this description field rather than the internal name.