<!-- [h]:[m]:[s] [P,*-2] or [h]:[m]:[s] [P,2-2] or [H]:[m]:[s] -->
<property as="xs:string" name="oxf.xforms.format.input.time" value="[h]:[m]:[s] [P,*-2]"/>
I wonder if the Orbeon time picker can display hours with preceding zero e.g. parse from 5:00pm becomes 05:00pm, and found above properties.
Also, can anyone explain what [P, *-2] and [P,2-2] mean?
Regarding your questions:
You can use [P,2-2] if you don't want dots in am and pm.
Adding leading zeros currently isn't supported. (If your organization has a PE or Dev Support subscription, you can contact Orbeon to see if this can be implemented as a "sponsored feature".)
And you can find more about the supported format in the section of the documentation about xf:input formatting.
Related
As of version 5.0 eXist-db no longer supports dynamically passing the option expand-xincludes=no to the Saxon processor during serialization. As such, I have to configure this in a Saxon config file. However this configuration does not seem to work - the xincludes are still being expanded in output.
Steps:
Following this comment and Saxon docs I created a configuration file called saxon-config.xml with the #xInclude="false" parameter:
<configuration xmlns="http://saxon.sf.net/ns/configuration" edition="HE">
<global xInclude="false"/>
</configuration>
I saved this in eXist's /etc/ directory and pointed to this file in the attribute in eXist's conf.xml:
<transformer class="net.sf.saxon.TransformerFactoryImpl" caching="no">
<attribute name="http://saxon.sf.net/feature/version-warning" value="false" type="boolean"/>
<attribute name="http://saxon.sf.net/feature/configuration-file" value="/Applications/eXist-db-5.2/etc/saxon-config.xml" type="string"/>
</transformer>
Yet the serializer still expands all the xincludes on output.
As a test to see if Saxon is reading the config, I put a deliberate error in the Saxon config file and Saxon objected.
Have I configured this for xInclude correctly?
--- adding more about workflow ---
Serialization in eXist 5.0 is performed in Xquery with the function fn:serialize().
I obtain a node (testing shows that this action does not expand xi:includes automatically in eXist) = $mydoc
I pass the node to the function with certain parameters, for example
fn:serialize($mydoc, map {"indent":true(),"method":"xml", "omit-xml-declaration":false()})
Output has expanded xinclude
I noticed this message on a recent mailing list, perhaps it's relevant.
My reading of this is that it's eXist doing the serialization with XInclude expansion, and this has nothing to do with Saxon. This doesn't solve your problem but hopefully it means you will be able to look in the right place for a solution; nothing you do with Saxon configuration options is going to make any difference.
Hi Ihe,
See the eXist documentation on XInclude, particularly the section on error handling:
https://exist-db.org/exist/apps/doc/xinclude
Joe
On Thu, Jun 18, 2020 at 7:50 AM Ihe Onwuka <ihe.onwuka#gmail.com> wrote:
5.2.0
On Thu, Jun 18, 2020 at 6:31 AM Jean-Paul Rehr <rehrjb#gmail.com> wrote:
Which version of eXist? Prior to 5.0 you can use
declare option exist:serialize "expand-xincludes=no";
in your Xquery declarations to allow/disallow Xinclude expansion (assuming you are using Xquery to execute the transformation). After 5.0...this no longer has an effect. Hopefully it will be reintroduced or another method discovered (see https://github.com/eXist-db/exist/issues/3446).
On Thu, Jun 18, 2020 at 11:12 AM Ihe Onwuka <ihe.onwuka#gmail.com> wrote:
A short while ago I wrote a transform that was supposed to transform a certain input element to an Xinclude element.
eXist blew up because it tried to resolve Xinclude call as soon as I attempted to store the transformation in the database.
Is that supposed to happen? Including the xsl list because am wondering whether this was a use case for namespace aliasing.
I have since solved the problem another way so the question is of academic interest only.
_______________________________________________
Exist-open mailing list
Exist-open#lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/exist-open
Hi fellow stackoverflowers! :)
I am wiring my application with adwords API, and want it to display reports based on the retrieved data. My problem is that I am using test account that have no data that could be used for reporting, and so far us I understand testing account don`t provide any. According to the https://developers.google.com/adwords/api/docs/test-accounts#developing_with_test_accounts I should fake data. I am totally fine writing tests and feed then with fixtures, expect I can't find any relevant example of how the response XML will look like so I can create my own fixtures.
For example:
I want to pull campaign performance report, and segment it by Week
<reportDefinition>
<selector>
<fields>CampaignId</fields>
<fields>Clicks</fields>
<fields>Impressions</fields>
<fields>Week</fields>
<predicates>
<field>CampaignId</field>
<operator>EQUALS</operator>
<values>111111</values>
</predicates>
<dateRange>
<min>20150201</min>
<max>20150601</max>
</dateRange>
</selector>
<reportName>Campaign Performance Report NAme</reportName>
<reportType>CAMPAIGN_PERFORMANCE_REPORT</reportType>
<dateRangeType>CUSTOM_DATE</dateRangeType>
<downloadFormat>XML</downloadFormat>
<includeZeroImpressions>true</includeZeroImpressions>
</reportDefinition>
Which gives me response:
<report>
<report-name name="Campaign Performance Report NAme" />
<date-range date="Feb 1, 2015-Jun 1, 2015" />
<table>
<columns>
<column name="campaignID" display="Campaign ID" />
<column name="clicks" display="Clicks" />
<column name="impressions" display="Impressions" />
<column name="week" display="Week" />
</columns>
</table>
What will be the response with actual data? How it is going to look like in case segmentation will be set to: Date, Month, Quarter, Year?
I have tried to find any xml example on the web and github without luck. Can you please share response examples or point me to the doc, where it says how can I "generate" data for my test acount?
Thank you!
eolexe, I am assuming you did not receive an error for the Campaign Performance Report you tried to fetch. If that is the case then that means there was no match for the predicates and date range you had entered. This why you do not have the rows element within the XML. Also some attributes are are not filterable. But I am pretty sure the CampaignID is. Take a close look at the API just to be sure. You need to migrate to version 201502 because 201402 is deprecated and 201409's sunset day is in July.
I have been working on AdWords API for reporting purpose for years, and I can tell you up till now there is still no official sample XML or CSV given. So I simply test the program using real account data...
I don't pick XML as the response type so I cannot really address your question, but you may wish to know that the XML response does not return a total row. That's why I always pick CSV/TSV format.
According to the documentation, LinkedTxns should be returned with both PurchaseOrders and Bills.
But, that feature does not appear to be working.
For example, this is the XML returned for the PurchaseOrder with DocNumber 1005.
<PurchaseOrder>
<Id>97</Id>
<SyncToken>6</SyncToken>
<MetaData>
<CreateTime>2014-06-24T16:21:18-0400</CreateTime>
<LastUpdatedTime>2014-06-25T10:42:03-0400</LastUpdatedTime>
</MetaData>
<DocNumber>1005</DocNumber>
<TxnDate>2014-06-24</TxnDate>
<PrivateNote>...</PrivateNote>
<Line>
<Id>7</Id>
<Amount>1600.0</Amount>
<DetailType>ItemBasedExpenseLineDetail</DetailType>
<ItemBasedExpenseLineDetail>
<ItemRef name="Transportation">21</ItemRef>
<UnitPrice>1600.0</UnitPrice>
<Qty>1.0</Qty>
<TaxCodeRef>NON</TaxCodeRef>
<BillableStatus>NotBillable</BillableStatus>
</ItemBasedExpenseLineDetail>
</Line>
<VendorRef name="...">3</VendorRef>
<APAccountRef name="Accounts Payable">51</APAccountRef>
<TotalAmt>1600.0</TotalAmt>
</PurchaseOrder>
And here is the screen shot from Quickbooks Online that shows that the linked transaction exists.
Is there a workaround for this problem? Is it caused by something that I can address?
LinkedTxn's are not supported for Bills at the time of this writing.
References:
See issue QBO-34591 on the following link:
https://developer.intuit.com/docs/0025_quickbooksapi/0058_faq/qbo_v3_known_issues
According to the release notes at https://developer.intuit.com/docs/0000_about_intuit_developer/0080_release_notes/quickbooks_api_release_notes This should have been addressed now.
I have implemented the fix client that request for market data. I have successfully logged on to the server but when the server sends us a MarketDataIncrementalRefresh message my application rejects with the message "Tag appears more than once" tag for which it is indicating is 55. Can you please help me in resolving it?
The message it rejects is:
8=FIX.4.2 9=196 35=X 34=14 49=Xenfin 56=newchange.api -price 52=20140528-08:54:32.144 262=156 268=2 279=1 269=0 278=B 55=EUR/USD 270=1.36201 271=1000000.00 279=1 269=1 278=A 55=EUR/USD 270=1.36205 271=1000000.00 10=133
and in my config file I have used no data dictionary and set UseDataDictionary=N
This usually means you have a configuration or DataDictionary problem, or both.
Configuration problem: Your config should have UseDataDictionary=Y, and DataDictionary=path/to/xml (or AppDataDictionary= and TransportDataDictionary= if you're on FIX5).
DataDictionary problem: Your counterparty has probably added custom fields to the message, and your DD hasn't been properly updated to reflect them. When parsing repeating groups, when the QF/n parser finds a field that doesn't belong (per DD) to the group, it assumes the group has ended. Any fields after that are considered to be outside the group.
You need to edit your DD file to reflect any changes that your counterparty has made to the standard message set. This will probably include adding custom fields, and may include rearranging field orderings or adding fields to groups that they don't normally belong in. See this page for more info about editing your DD:
http://quickfixn.org/tutorial/custom-fields-groups-and-messages
That's because you have a repeating group, once for bid, once for offer
8=FIX.4.2
9=196
35=X
34=14
49=Xenfin
56=newchange.api -price
52=20140528-08:54:32.144
262=156
268=2
279=1 269=0 278=B 55=EUR/USD 270=1.36201 271=1000000.00
279=1 269=1 278=A 55=EUR/USD 270=1.36205 271=1000000.00
10=133
and you're not handling it properly.
Using orbeon-4.1.0.201304182144-PE, I'm having a problem with Smart Date completion.
I've included the configuration property:
<property as="xs:string" name="oxf.xforms.format.input.date" value="[D]/[M]/[Y]"/>
to take European-style dates as input.
The condition for Smart Date completion:
When the oxf.xforms.format.input.date property starts with [D: e.g.
20/10
from Input Control-Forms doesn't seem to trigger. I get:
Input Output
20 20/5/2013 (Correct)
20/5 Not Valid (Incorrect, should be 20/5/2013)
20/5/13 20/5/2013 (Correct)
5/20 20/5/2013 (Incorrect, should be Not Valid)
Is this a bug?
This was a bug, and it is now fixed. The fix will be in the next release of Orbeon Forms, which at the time of this writing will most likely be 4.2.