I'm seeing an error when typing into a suggest box:
Thu Dec 08 10:45:58 GMT-700 2016
Speckle models do not support distinct sorted field values. Error: Speckle models do not support distinct sorted field values.
E
Thu Dec 08 10:45:58 GMT-700 2016
Query for field suggest oracle.: (Error) : Speckle models do not support distinct sorted field values.
E
Thu Dec 08 10:45:58 GMT-700 2016
Query for field suggest oracle. failed.
Value of the suggest is set to:
#datasource.query.filters.project._equals
and the suggestions are set to the datasource and field project.
I have also un-checked "Value is a record" as that is an error already in the editor.
I can use a normal text box and the same value to filter the data which works fine but would prefer the ability to select from suggest.
Support for using suggest text field with SQL is coming in the next few weeks. I will respond to this question again when it is added.
CloudSQL support for Suggest text field is released. Please give it a try.
Related
A short description of the issue:
I can't make a new page, 2 data source relation function in my app (which has similar existing pages with relations that work). The new relation always produces the following error on the parent table:
E Fri Nov 08 08:10:55 GMT-700 2019
TypeError: Cannot read property "EkYkTNJF93VWDxnS7Gi1OIIBSsHXTZ7H" from null.
E Fri Nov 08 08:10:55 GMT-700 2019
Creating new record: (Error) : Cannot read property "EkYkTNJF93VWDxnS7Gi1OIIBSsHXTZ7H" from null.
at Apex_Office_Time.Table1Panel.Table1.Button1.onClick:1:19
E Fri Nov 08 08:10:55 GMT-700 2019
Creating new record failed.
I I am always able to produce the error even when I start a new app from a blank template. The error will occur & not show the new record. Yet if I refresh, the record will be there. Existing apps with similar relations always work.
001 Here is the data source relation between the 2 data sources
Here is a newly set up Google cloud SQL data source "Apex_Office_Time"
Here is the Second Data source "Apex_Office_Time_Details"
Here Is the Page "Apex_Office_Time" which contains a table. The blue + button should create a new item on the table. It does when there is no relation between the data sources
Here is a shot that of the page that show the data source for the table is related to "Apex_Office_Time"
Here is the generated preview before I hit the + button
Here is the generated preview after I hit the + button & complete with error code
Here is the generated preview after I hit the + button, and after I manually hit the refresh button on my browser. I get the same results in Chrome, Firefox, & MS Edge
Further points of note:
When I set up a table that generates items for the "many" side of the relationship "Apex_Office_Time_Details", new items for this table are created without issue.
I just added a third data source to the mix "Apex_Office_Test". I then made "Apex_Office_Time_Details" to "Apex_Office_Test" a one to Many relation. I then tested to see if I could create items in "Apex_Office_Time_Details" without issue as before. I was successful. I then tested to see if I could create items in "Apex_Office_Test". I was successful. I then deleted the "Apex_Office_Time" data source and retested the other 2 tables and their data sources. I was successful. It seems very odd, but its working. I am going to continue testing based on this line.
Success! Evidently there is a minimum length for the names in data sources. The number fields "b" & "bh" in the data source "Apex_Office_Time_Details" was the issue. When I deleted them the table worked. Then I tried renaming the fields to "Billed" & "Billable_Hours" and everything seems to be working
Success! Evidently there is a minimum length for the names in data sources. The number fields "b" & "bh" in the data source "Apex_Office_Time_Details" was the issue. When I deleted them the table worked. Then I tried renaming the fields to "Billed" & "Billable_Hours" and everything seems to be working
I have question.
I am programming a example Project.
I have a EDT called Joining and this EDT is of type Date.
I did put it in my table employment and in my form employment.
Now I want to have this field, that when entry one date for a dataset that I can never edit it again.
How do I do that ?
Do I have to write Code ?I guess.
With Kind regards
Khashayar
On your table Employment, select the field and set the AllowEdit=No and leave the AllowEditOnCreate=Yes.
This will let users enter the date when they're creating the record, but not edit after.
You can not set this at the EDT level.
I have the output schema which should look in the following format
Header
Memeber 01
Benefit 01
Benefit 02
Memeber 02
Benefit 01
Benefit 02
Benefit 03
Trailer-Count 09
The Trailer should have the field element called count which should hold the count of the no.of records. How should we approach this should I create a custom pipeline component or can we do this through mapping. Any help is greatly appreciated.
Not sure what's your message type, If your send port is designed to receive individual member messages then assembly them together, yes, a custom pipeline component shall be used.
If your message already have the Header and Trailer defined, you can simply use a map to count the member nodes count without using a custom pipeline component
I have a DateType input in my formBuilder. In my form, when I put 12/12/1500, it changes the date to 12/12/1901. I use it with widget single_text, format dd/MM/yyyy and input datetime
I have removed all the validations constraint on the field, so it has to come from the Type
How can I change this unwanted behaviour?
From the documentation, http://symfony.com/doc/current/reference/forms/types/date.html#input
"If timestamp is used, DateType is limited to dates between Fri, 13 Dec 1901 20:45:54 GMT and Tue, 19 Jan 2038 03:14:07 GMT on 32bit systems. This is due to a limitation in PHP itself."
Try changing the 'input' option for the your date field.
Issue: Drupal Views module only displays Wed Dec 31, 1969 for date fields
I have created a CCK content field type called field_gse_event_start_time. I also have several views displays that use this field - a calendar view, a table view, and a block view for the home page. I also have a themed node template for the event content type that this field belongs to.
The start time field requires a 'to' date as well as a from date. I have tried to change the type of the field_gse_event_start_time to date, datetime, and datestamp. In all cases the node display of the fields is correct, but any view displays Wed Dec 31, 1969.
I am sure this is due to some casting error or null, which adjusts to this pre-epoc value.
I just don't even know where to begin or how to fix.
Some config
Drupal core 6.26
ctools-6.x-1.8.tar
date-6.x-2.9.tar
views-6.x-2.16.tar
You probably know that the 1969 date is returned by date() when you pass it an invalid epoch time and you have a negative timezone offset. So, date() will default the invalid epoch to 1, and the timezone offset makes it pre-epoch.
Why this is happening in your Drupal view is probably because of a views field handler expecting the wrong format. What field type are you using for field_gse_event_start_time?