Overview
The Groundswell Calendar Display, powered by ToastUI, gives designers the ability to quickly have a modern calendar display in their sites and dashboards with the simplicity of a single component. The dense, versatile display supports different calendar views with styling matching your site’s accent color. Example interfaces and utility rules are attached, which demonstrate usage and features of the component.
Key Features & Functionality
That's something I've encountered as well, and I took it up with Appian Support as I consider it a product issue rather than a plug-in issue, as the plug-in works as expected regardless of the warnings. I was unable to get a resolution however.
I just installed this plugin and am having this same issue. Specifying the version does remove the warnings, however when I save the interface the version identifier is removed and the warnings return. Any suggestions for resolving this? I have attached an image of the parameters that are causing the warnings. Thank you.
I suggest using an explicit version identifier like calendarDisplayField_v7 to make sure you are using the latest. That should remove the warnings
Hello,
I am getting some invalid parameter warnings for calendarDisplayField. Any ideas what may be causing this issue?
very peculiar, I only get the error when I drag the file from windows explorer. Selecting the file to upload works fine.
I've never seen this error message in any application before, so I just connecting with Appian support.
I did just download the sample app and was able to successfully import, so this could be an environment specific issue.
tried to import the sample application and received the following error:
Error Evaluating UI Expression Expression evaluation error [evaluation ID = 531a0:80b5f] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: Expression evaluation error at function a!packageTypeFunction [line 4]: Cannot invoke "com.appiancorp.ix.ParametersFile.getParametersDoc()" because "this.parametersFile" is null]
There appears to have been a packaging bug that caused an issue in non en-US locales. This has been submitted to Appian for release as v7.8.0, and that should come out in a week or so.
According to the documentation, the language Spanish (ES) is allowed, according to the documentation of the component within Appian it is Spanish (Mexico). However, none of the language settings mentioned work as they should please see image.
Please tell me if there are any adjustments or anything additional that I need to do so that it is reflected correctly.
Kind regards!