I have used jqm calendar for events list. Its showing perfect and showing list according to date. but now I want to link events list to their detail page so I need to pass html code means summary as a link so when list show below the calendar its can be likable and when I click it redirect to its detail page. below are my code
{"summary": Event Name',
"begin": new Date(2015,8,24 ),
"end": new Date(2015,8,24)}
but its showing me title as it as above not making it linkable title.
please sugggest
I found solution for this you can pass url in url key. see below code:-
{"summary": "Test Event name here",
"url":"your url here",
"begin": new Date(2015,8,24 ),
"end": new Date(2015,8,24)
}
Related
I have a Docker Image where jsReport is rendering a custom doxc file to a pdf. I have normal string values like firstname and lastname + some checkboxes depending on previous user input.
Evening works fine for the string values, but the checkboxes will not get rendered.
After rendering, it looks like this:
The data looks like this:
{
"customer": {
"fullName": "John Doe",
"birthDate": "10.10.1999",
"companyRegistrationNumber": " / AB123456",
"fullAddress": "Street 1234 B5",
"email": "mail#support.com"
},
"date": "11.09.2022",
"ready": true
}
It is rendering something, it even uses the "ready" value because it displays the same string as "true", but it is not displaying a checkbox
The docxCheckbox helper call needs to be placed in the title of the word checkbox.
See the documentation
https://jsreport.net/learn/docx#forms
And the demo
https://playground.jsreport.net/w/anon/DtnCaXMs
The property menu is not available with the right-click menu. It is only in the developers tab
I am working on a Zapier integration for an online form builder. Each unique form for our users has lots of long, auto-generated field names.
We have a trigger called “New form entries”, which polls our server for form entries, and comes back like this:
[
{
"id": "6209aee326baa600224d822c",
"email_907058157108782": "test#test.com",
"phone_589083232390193": "12345",
},
{
"id": "61fd629f19408200225e1893",
"email_907058157108782": "test#test2.com",
"phone_589083232390193": "54321",
},
]
However, this results in end users seeing these really long, gross field names in the Zapier interface:
My question: how do I get Zapier to display friendly labels to the user, whilst using the unique field IDs behind the scenes?
I’m thinking of returning something like the following (each object represents a form entry, , but I need to know how to actually use “friendlyFieldName” and “value” in Zapier!-
[
{
// the id for the entry
"id": "62179ec5ab9daa0022df7d1d",
// the id for the first field entry
"text_576692390099896": {
// a friendly name and value for zapier
"friendlyFieldName": "What is your favourite colour?",
"value": "Blue"
}
}
]
Thank you :)
You can define output fields labels in outputFields. Here are the reference document that you can follow: Output Fields
I am using the jira rest api in python (jupyter notebook) and want to get the display name of a custom field from Jira.
The custom attribute I am using represents Team Name in Jira. ex. 202 = "A Team", 204 = "The Brew Team", etc.
when I for loop I am able to get team id's but I'd like to get the display names ("A Team", "The Brew Team", etc.)
for item in project:
team = item.fields.customfield_26588
print(team)
Is there a way to get the actual display names from the custom field programatically?
Jira issue doesn't hold that information, jira instance does, since they associate the field with the issueType
you can get ALL the fields form the jira Instance, and match them against the ones in the issue with the id.
jira = JIRA(server=SERVER, basic_auth=(USER, PW))
issue_x = jira.issue("TEST-101")
all_the_fields = jira.fields()
for i in all_the_fields:
for xx in issue_x.raw['fields']:
if i["id"] == xx:
print(i)
Object of custom field looks like:
"customfield_1234": {
"required": false,
"schema": {...},
"name": "Name",
"allowedValues": [...]
}
If you want to have name of the custom field itself, you can get it from 'name' attribute of object.
So, in your code you need to use:
print team.name
I am unable to create or update a SharePoint Online listitem that contains a hyperlink field using Microsoft Graph. I can create or update items to the same list if I remove the hyperlink field from the body of the API call.
For update, I am sending a PATCH request to:
/v1.0/sites/<site>/list/<listid>/items/<item>/fields
with the following headers:
"Authorization" : "Bearer <token>"
"accept" :"application/json;odata.metadata=full;odata.streaming=true"
Here is the body:
{
"myUrl": {
"Description": "http://www.google.com",
"Url": "http://www.google.com"
}
}
I will get the following error message in response:
{
"error": {
"code": "invalidRequest",
"message": "The request is malformed or incorrect.",
"innerError": {
"request-id": "cfe30f57-31ba-4341-89e9-2c1bd4e15539",
"date": "2017-11-10T21:55:30"
}
}
}
It is worth noting that I can update other fields in the list item using the exact headers and target URL, as long as there is not a hyperlink field in the json body.
The format I am sending is the exact format I receive the URL field in when I do a GET. Does anyone know the appropriate format for sending URL fields back to SharePoint?
Update 1/8/2018
I posted this same issue to Microsoft's Graph Github on 11/11/2017 and they have yet to provide an answer. I have heard unofficially that REST operations on listitems that have a nested structure (e.g. hyperlink, user, taxonomy) are not supported at this time. Here is a link to the issue just in case they answer it later: https://github.com/microsoftgraph/microsoft-graph-docs/issues/1965
I do have a workaround for hyperlink fields that I am using. I changed the column on the SharePoint List that was previously a hyperlink to a "Single line of text" field. When a hyperlink is entered in a Single line text field, it is showing as a underlined and clickable link when you view the event in a browser. You can't use alternate text if you have a long and ugly URL like with the hyperlink field type, but it works!
Looks like the body has the values in reverse. You have your URL in the Description Field and the Description in the URL field. Try:
{
"myUrl": {
"Description": "google",
"Url": "http://www.google.com"
}
}
I am new to Docusign api and I am trying to post values from my form into a template. To be honest, I am not sure if I even created the custom fields properly or if there is some special way to set them into the form other than just creating a text field with a name.
I have read through the docs and recipes and about a dozen or more stack posts.
I am using rails and my fields post just fine but it's my tabs that do not. I read somewhere that I am supposed to use tabs and not custom_fields. Not sure if that's totally correct but that's how I've interpreted it.
Here is my current code:
body: {
"emailSubject": "DocuSign API call - Request Signature - Boom",
"templateId": "e1d5bce1-9757-4ffe-881b-054aa9139f2f",
"templateRoles": [{
"email": "#{renter.email}",
"name": "#{renter.background.legal_name}",
"roleName": "Lessee"
},{
"email": "#{#manager.email}",
"name": "#{#manager.name}",
"roleName": "Lessor",
"tabs": {
"texttabs": [{
"tabLabel": "Rent",
"value": "#{#lease.rent}"
},{
"tabLabel": "Address",
"value": "987 apple lane"
}]
}
}],
"status": "sent"
}.to_json
baseUrl that I am sending to:
"https://demo.docusign.net/restapi/v2/accounts/my_id/envelopes"
In your texttabs section, you should be passing in the following parameters at a minimum per tab: tablabel & value.
tablabel is the name of the tab that you have defined on the template. So from what I can tell, you have a text box on your template called Address. So you should put "tablabel":"Address".
value is what you would like to pre-populate in the tab. Looks like you have that correct.
You do not want to use tabID as that is not a valid parameter in this flow. The API documentation details what parameters you can use: https://www.docusign.com/p/RESTAPIGuide/RESTAPIGuide.htm#REST%20API%20References/Tabs/Text%20Tab.htm?Highlight=data%20tab
I also see an extraneous parameter of "Rent" under templateRoles section. That value will be ignored since it is not a valid parameter.
Turns out the problem was not with the code but with the setup within docusign. Make sure that you are setting up your tabs correctly and if you want to replicate a field multiple times make sure that they all share the same exact name.