Current filter:
                                You should refresh the page.
                                  • Hello,
                                    I have installed new XAF v18.1.3 and now all date in listview are showed in the long date format. In v17 was in short date format to default. In attachment an example image.
                                    I would to set all dates in short date globally.
                                    How can I risolve the issue?

                                    Thank you,
                                    Rossano

                                Show all comments
                                • Dennis (DevExpress Support) 06.07.2018

                                  Hello Rossano,

                                  I checked two our demos (https://demos.devexpress.com/XAF/MainDemo/ and https://demos.devexpress.com/xaf/simpleprojectmanager/) and could not detect any changes in this regard between v17.X and v18.1. The default display format value for System.DateTime is {0:d}.
                                  It looks like something has changed in your custom code.
                                  In order to do this, look for any code and settings that touch the DisplayFormat and DefaultDisplayFormat XAF APIs or customize the control settings directly.
                                  If you happen to replicate this with our demos, provide us with the exact repro steps. We will be more than happy to research this further.

                                • Rossano Palazzo 06.07.2018

                                  Hello,
                                  I found that the issue exists when I insert the Italian satellite assemblies for translate.

                                  I hope you can help me with this problem.

                                  Thank you,
                                  Rossano

                                • Rossano Palazzo 06.07.2018

                                  Other correlate issues in attachment.
                                  Thanks 

                                • Dennis (DevExpress Support) 06.07.2018

                                  We need some additional time to research this behavior. Please attach your v17.2 and v18.1 satellite assemblies as well. This will help us test the same scenario. For now, I only checked that the localization service provides the correct DefaultDisplayFormat  default values.
                                  In the meantime, you can bypass this behavior as follows:

                                  1. Use Localization Service  to modify your translations as needed.
                                  2. Use the Model Editor to translate these strings directly in the application. Most likely, the DisplayFormat and DefaultDisplayFormat  attributes hold incorrect values.
                                  Refer to the https://docs.devexpress.com/eXpressAppFramework/113250/task-based-help/localization/how-to-localize-an-xaf-application and https://docs.devexpress.com/eXpressAppFramework/112754/getting-started/comprehensive-tutorial/ui-customization/format-a-property-value topics for more information.
                                • Rossano Palazzo 06.07.2018
                                • Dennis (DevExpress Support) 06.08.2018

                                  I tested your assemblies with our MainDemo.Web for v17.2 and v18.1 and could not see the differences. Date properties were displayed equally.
                                  Would you please attach your v17.2 sample that worked fine with the same assemblies + screenshot showing the expected result in the UI? It is possible that there are other settings that affect this behavior.

                                • Rossano Palazzo 06.08.2018

                                  Hi,
                                  now the issue also exists with v17.2!
                                  But I found old satellite assemblies for translate always v17.2 that work well!

                                  In attachment the demo video and old satellite assemblies v17.2.

                                  Current satellite assemblies v17.2 and v18.1 do not work well .
                                  I hope you can help me with this problem.

                                  Thank you,
                                  Rossano

                                • Dennis (DevExpress Support) 06.09.2018

                                  Hi Rossano,

                                  My MainDemo.Web app works fine with the old satellite assemblies. I am researching the differences between them.

                                • Rossano Palazzo 06.11.2018

                                  Ok thanks.
                                  in attachment another satellite assemblies  anomaly for double field.

                                • Rossano Palazzo 06.12.2018

                                  Hello,
                                  you solved?
                                  How long do you expect to solve the issue? 

                                • Dennis (DevExpress Support) 06.13.2018

                                  Hello Rossano,

                                  I hope to answer you today on this. Please bear with me.

                                1 Solution

                                Creation Date Importance Sort by

                                As I guessed in my very first reply to you, the DisplayFormat, DefaultDisplayFormat, EditMask and DefaultEditMask attributes under the ViewItems | PropertyEditors | XXX nodes contain incorrect values. They come from the DevExpress.ExpressApp.Web.v1X.X.resources.dll assembly.
                                For instance, there are extra spaces for the System.Double, System.Single and System.TimeSpan nodes. DefaultDisplayFormat for the System.Decimal node should be {0:C}. DefaultDisplayFormat for the System.DateTime node should be {0:d}. You should additionally fix the AboutInfoString attribute from "{0:ProductName} < br > {0:Version} < br > {0:Copyright} < br > {0:Description}" to "{0:ProductName}<br>{0:Version}<br>{0:Copyright}<br>{0:Description}". Refer to the How to: Change an Application Logo and Info article for more information.
                                I suggest you check out other values as well.

                                To avoid the problem in your app, do the following:

                                1. Remove the DevExpress.ExpressApp.Web.v1X.X.resources.dll assembly from the "it" folder;
                                2. Follow my second comment on June 7th to localize incorrect values using the Localization Service or Model Editor tools.
                                >>
                                In the meantime, you can bypass this behavior as follows:
                                1. Use Localization Service  to modify your translations as needed.
                                2. Use the Model Editor to translate these strings directly in the application. Most likely, the DisplayFormat and DefaultDisplayFormat  attributes hold incorrect values.
                                Refer to the https://docs.devexpress.com/eXpressAppFramework/113250/task-based-help/localization/how-to-localize-an-xaf-application and https://docs.devexpress.com/eXpressAppFramework/112754/getting-started/comprehensive-tutorial/ui-customization/format-a-property-value topics for more information.
                                <<

                                Let me know if you require additional assistance.

                                Thanks,
                                Dennis

                                P.S.
                                Our team will also see to removing incorrect translations from the Localization Service, though I cannot give you any exact ETA for this. The wrong values were included into the service by default because of the internal mechanism. If several customers translate a certain attribute value the same way, this value becomes the default value. This mechanism exists to save time for other users. However, we would certainly need to tune it up, e.g., by increasing the threshold to be more trustworthy.

                                • Dennis (DevExpress Support) 06.27.2018

                                  Rossano,

                                  In your particular case, you should additionally fix the AboutInfoString attribute from "{0:ProductName} < br > {0:Version} < br > {0:Copyright} < br > {0:Description}" to "{0:ProductName}<br>{0:Version}<br>{0:Copyright}<br>{0:Description}". Refer to the How to: Change an Application Logo and Info article for more information.