How to format dates and language properly in 360Bind and 360Cast

How to format dates and language properly in 360Bind and 360Cast

Environment

  • 360Bind (within 360Suite)

  • 360Cast (within 360Suite)

Symptom

  • Labels/messages in the UI or exported outputs appear in the wrong language.

  • Exported files show incorrect regional formats, such as:

    • Date format (dd/MM/yyyy vs MM/dd/yyyy)

    • Decimal separator (comma vs dot)


Cause

  • In 360Bind, the Default Export Language is not set to the intended language.

  • In 360Cast, Export locale is not configured correctly, so exports do not apply the correct language + regional formatting.


Resolution

360Bind — Set Default Export Language (new UI)

  1. Open Admin Console > 360Bind.

  2. On the landing page, locate the Default Export Language field.

  3. Set Default Export Language to the target language (e.g., English, French).

  4. Save/apply your changes (if required by your environment).


360Bind — Set Default Export Language (old UI)

Use this procedure if your Admin Console still shows the classic navigation.

  1. Open Admin Console > 360Bind.

  2. Go to General Settings (or Settings, depending on your version).

  3. Set the default export language to the target language (e.g., English, French).

  4. Save/apply your changes (if required by your environment).



360Cast — Set Export locale (output language + regional formats)

  1. Browse to Scheduling & Report Bursting Task and open your 360Cast task.

  2. In the Options tab, configure Export locale to control both language and regional formatting in generated files:

    • Static value: select one locale for all outputs (e.g., English (United States) – en-US, French (France) – fr-FR).

    • Dynamic value: map Export locale to a column in the destination list so each recipient’s export uses their locale
      (values in the column must match the locale names shown in the UI).



    • Related Articles

    • "Invalid tag: FORMAT_DICT" error

      Symptoms After upgrading a BusinessObjects (BOBJ) environment, you may encounter the error with 360Suite feature like 360Cast or 360Bind: Unexpected exception: Failed to parse document. Invalid tag: FORMAT_DICT These features typically work with ...

    • ERR_WIS_30272 Maximum character output size limit reached in Bind Export tasks

      Symptom Bind Export tasks with Webi documents exported with the XML format end up in warning/failed state with the following error: Error: com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: Maximum character output ...

    • Bind Content Comparison Task : GC overhead limit exceeded

      Introduction This article explains how to resolve a GC overhead limit exceeded memory error that occurs during a 360Bind comparison task. Environment Product: 360Suite Product version: all versions Database: all Symptoms A 360Bind comparison task ...

    • How to properly enable an Administrator key in 360Suite

      Procedure Log into the Administrator Console. Navigate to the License tab. In the Keys block, paste the license key provided. Navigate to Administrators block. This is where the BOBJ user accounts can be mapped as 360Suite administrators up to the ...

    • Excel Destination List Template

      Below are examples of destination values for a Destination List to use in 360Cast Tasks. Destination Type Format Year State Default BOBJ FY2004 USA C:\Users\Administrator\Documents\Cast\ File PDF FY2005 France bobj-admin@wiiisdom.com Email XLSX ...