I am executing a query against Alfresco using FTS. I want to find files that have my:property empty. This is part of my query:
AND (ISNULL:"my:property" OR ISUNSET:"my:property" OR =my:property:"")
When testing I discovered that this will not find my file when my:property is set to an empty string. When I change the query to this it does find that file:
AND (=my:property:"")
It seems to me that the OR statements aren't executed appropriately.
Can anyone tell me what I'm doing wrong here?
Edit: I'm using Alfresco Community 5.1f
Related
I've edited some existing visual queries of Blog 4.0 application and when I was debugging it - it worked perfectly. But then on page it stopped working. Any attempt to use key with Data like Data["Posts"] raises System.Collections.Generic.KeyNotFoundException. App.Query["Blog Posts List"]["Posts"] returns something, but any attempt to access its fields raises another exception (don't remember the name, but it said that there's no such member inside that object).
I didn't rename queries, I didn't change application settings. I just edited logic of 2 queries. I renamed 1 wiring endpoint name across 3 queries in whole chain.
How do I debug it? How can I see what does cshtml receive from database so I don't guess and put my crystal ball away?
In general, App.Query["Name of Query"] will get you the streams of data. You usually need to convert it using AsDynamic() or AsList() to something you can work with.
This should help some; What is Data?
If you're just running into problems with field names, you probably forgot the AsList or AsDynamic, just like #accuraty-jeremy mentioned.
For real debugging, go to insights, you'll see what happens - but in your case it probably won't help, because your working with an object that's not dynamic (so doesn't support .FirstName) until you AsList/AsDynamic it.
My bad: I confused two different files - _List.cshtml and _List Paging.cshtml. So I was searching for an error in the code of wrong file.
I currently have a Gatsby project based on the Gatsby-Ghost-Starter project. The Ghost schema is no longer being generated in Gatsby for some reason, and I can't seem to figure out why. As a result, I get the following error:
There was an error in your GraphQL query:
Cannot query field "icon" on type "GhostSettings".
If you don't expect "icon" to exist on the type "GhostSettings" it is
most likely a typo. However, if you expect "icon" to exist there are a
couple of solutions to common problems:
If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your
development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields
you can query and what shape they have
You want to optionally use your field "icon" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the
GraphQL schema. A quick fix is to add a least one entry with that
field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want
to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema
for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
This error message is basically repeated for every page and query field that uses anything related to the Ghost schema. I pulled up the GraphiQL explorer to see if I could access the fields there, and it indicated there is no schema available (as seen in the screenshot here). I tried rolling back to previous commits, deleting .cache and node_modules, updating all packages, and re-cloning the repo to no avail.
My latest commit was able to compile with no problem in the production environment, so I think it's some sort of misconfiguration on my machine...The environment variables are all identical, and I tried using the production Ghost server as my "ghost-source" on my local machine (since I know it works if the production build compiled successfully), but nothing changed. I've been stuck on this for days and have no idea how to even debug what's happening right now. Any advice/insights would be greatly appreciated.
I need to set up a collection of Washing Machine manuals in a way that I can then set up queries against the paragraphs that are included in the manuals. My understanding is that Element Classification should help achieve that goal
https://console.bluemix.net/docs/services/discovery/element-classification.html#element-classification
Using the tooling, I set up a collection and uploaded the following file, selecting "Default Contract Configuration" : https://www.samsung.com/us/pdf/wf338_manual.pdf
Why is this document upload failing?
To get more error details, I tried using the API with Postman but am unable to run the Add Document query as described here https://www.ibm.com/watson/developercloud/discovery/api/v1/curl.html?curl#add-document
The document is in PDF format and in text form, and is less than 50MB.
Does anyone know what is happening or has a suggestion on how to resolve?
Thanks
I am on Oracle Reports 10g, and I have an RDF that I would like to schedule to run and create a PDF on my local folder. I thought this URL would work:
http://mywebsite.com/reports/rwservlet?server=RptSvr_core2pweb99_asinst_1+userid=myuserid/password#database+report=/home/oracle/middleware/Oracle_FRHome1/forms/v10suite/GL573.rdf+destype=file+desname=c:\temp\GL573.pdf+desformat=pdf+P_unit=26014+P_TTLCOMP_YN=N
My report is on an app server. If I changed the DESTYPE from FILE to CACHE and removed the DESNAME in the URL above, it would create a report in the browser.
Please advise, what am I missing?
OR, is there some way to create a report executable that I can run from my Windows 7 PC to create a PDF? (I was able to do this on Windows XP with RWRUN.)
Only problem is of using wrong concatenation operator + which should be &, instead, before parameter names as in the following string :
http://mywebsite.com/reports/rwservlet?
server=RptSvr_core2pweb99_asinst_1
&userid=myuserid/password#database
&report=/home/oracle/middleware/Oracle_FRHome1/forms/v10suite/GL573.rdf
&destype=file
&desname=c:\temp\GL573.pdf
&desformat=pdf
&P_unit=26014&P_TTLCOMP_YN=N
P.S. without spaces inside string as in your case.
I have a Report Parameter called "jndiURL" (I've tried other names, the same problem occurs) that is passed into a BIRT Report. In the Properties of my Data Source, I go to Property Binding and set the JNDI URL to:
params["jndiURL"].value
I accept the changes and the window closes without errors. Then I create a data set, set up a query, preview the results and accept the changes. At this point I get an error that says:
Error evaluating Javascript expression. Script engine error: Report parameter "jndiURL" does not exist.
Script source: <inline>, line: 0, text:
params["jndiURL"].value
After this error is closed the data set can no longer resolve itself (i.e. the list of available fields disappears). Removing the Property Binding in the Data Source allows you to create Data Sets normally, but as soon as you add the Property Binding again, the data set is unresolvable.
I'm taking over report creation from someone else who is no longer here and this is how their reports are all set up so they might have been using another version of BIRT or found a work around. I believe one solution is to add a script to set this property when the report runs, but I would like to avoid that.
Any ideas?
I'm using BIRT 2.6.2 for Eclipse (All-in-One version).
This bug was fixed in the latest version of BIRT. If you cannot update BIRT to the latest version, a patch exists for 2.6.2