annesophiecy​ - i am having the same issues and I have tried explicitly casting the memo field using a PostgreSQL command (memo)::VARCHAR but it didn't seem to fix the issue. Can you help with how you did the actual conversion of memo (TEXT) type to String using a SQL function?

@adobeaspirant - no you cant. That version of forms that comes pre-installed with AEM Quickstart is a "prevew" version and is missing most of the required functionality for the form to work properly. We have actually had a few clients mistakenly think that they had adaptive forms and could do stuff ...

Ok I found the solution. For some reason, this works individually or if you fork the input into each activity instead of running them in series.It would be great to know why this works and the other doesn't but i suspect it's "working as designed"

We can create and update segments based on Declared Id fine. We did find an issue (feature?) where a delivery adds a foreign key (@broadLog-id) to the target schema that you have to remove to get Declared Id segment update working. Once you remove that, the Declared Id segment updates fine.However, ...

Yes we are still seeing this behaviour. Incident 181014-000111 has been logged for this issue

Currently the date formats default to MDY format and there is no way to change this. Since most of the world uses DMY format [1] it doesn't make sense to have MDY as a fixed format. It's confusing especially with ambiguous dates (e.g. 10/4/2018 could be 10th April or 4th October).There should be a l...

Can you provide a bit more information? e.g.Where are you seeing this error? Workbench? Designer?How many unique nodes are actually in your schema?Is your schema well formed? [1]Does it contain any recursive nodes? [2][1] W3C XML Schema (XSD) Validation online [2] IBM Knowledge Center

I am looking at the graph provided by the Triggers page and it is showing totally incorrect data represented on the graph. The number is showing correctly but the graph in no way represents the number or dates of triggers fired. This is the same for all triggers.Is this expected behaviour?

I am trying to troubleshoot Triggers and the pipelined process using the help at How to use Experience Cloud Triggers with Adobe Campaign Classic It talks about a "pipelined status page" (No triggers are retrieved > Step #4 Look for errors in the pipelined status page. trigger-discarted, trigger-fai...

The DropDownList can be programmatically populated in the initialise event using an array of key=value pairs [1] on the items property [2]. So for your particular example, to populate the list starting at the current year and running for 5 years would look something like:(on the initialise event)var...