Busca respuestas existentes a tus preguntas de productos y soporte.
Familiarízate con nuestro sitio de soporte y aprende las mejores prácticas sobre trabajar con nuestro equipo.
Manejar Peticiones de Servicio. Ve y actualiza peticiones de servicio tuyas o de otros miembros de tu organización.
Reporta un nuevo problema a nuestro equipo de soporte técnico.
Explora recursos que serán útiles para poner en marcha tu implementación y asegurar un lanzamiento exitoso.
Accede a tu cuenta OCI.
Encuentra documentación del producto para versiones vigentes de B2C y bibliotecas de documentación para soluciones de servicio relacionadas.
Tendrás las herramientas para mejorar la experiencia de los clientes al aprender todo lo que nuestro producto es capaz de hacer.
Encuentra enlaces para la documentación de APIs, Procesos Personalizados, Portal de Clientes, y la Estructura Extensible de la Interfaz de Usuario del Navegador para Agentes (BUI).
Explora cómo los aceleradores son diseñados para demostrar cómo un escenario de integración podría ser construido usando integraciones públicas y las capacidades de extensión del servicio de Oracle B2C.
Prepárate para una transición exitosa al revisar cambios y mejoras próximas a ser lanzados.
Explora webinarios, eventos, y kits de características para aprender sobre las características, funcionalidades, y mejores prácticas para el Servicio B2C brindado por técnicos expertos en el área.
Oracle MyLearn ofrece un portafolio de recursos de aprendizaje basados en un modelo de suscripción gratuito y de paga para adquirir habilidades valiosas, acelerar la inclusión de la nube, incrementar la productividad, y transformar tu negocio.
Empodera a tu equipo con las habilidades para implementar, configurar, manejar, y usar tus aplicaciones con el Entrenamiento de la Nube para la Experiencia del Cliente.
Nuestro objetivo es facilitar un entorno amigable y solidario, donde los miembros pueden colaborar fácilmente entre ellos sobre soluciones y mejores prácticas.
Realiza y responde preguntas específicas a B2C.
Este es un recurso fascinante con el propósito de ayudar con el Análisis de la Nube del Servicio de Oracle.
Comparte ideas de cómo mejorar el producto y solicitudes de mejoras con el equipo de desarrollo de Oracle, mientras colaboras con otros clientes y socios de Oracle.
Actualiza tu número telefónico, preferencias de notificaciones por correo electrónico, y preferencias de contacto para incidentes de severidad 1 y 2.
Consulta los gestores de contactos dentro de tu organización.
Encuentra información de contacto del Gerente Técnico de Cuentas (TAM), y el Gerente de Éxito de Clientes (CSM) para tu organización.
When I add more than one table to a report, I have options to Toggle Join Type. What are the join types? What are table joins?
Environment:
Analytics Oracle B2C Service, All versions
Resolution:
Table joins allow you to link data from two or more database tables into a single query result. This allows you to view and display data from multiple tables in a single report. When you create a report that uses data from multiple tables, you can specify which type of join to use between the tables.
To successfully join information from two tables, each table must contain a data field that is common to both tables. The fields do not need to have the same name within each table, but MUST refer to a common element in both tables.
When tables are joined in a report, the icon used illustrates the join type. If the circle on the left is entirely filled in as blue, there is an outer join between the tables. If only the overlapping section of the icon is blue, the join between the tables is an inner join.
To determine how tables are joined in a report, use the steps below:
For example, in the Oracle B2C Service database, the incidents table includes the assigned field which specifies which staff member the incident is assigned to by the account ID. The accounts table lists all staff accounts and includes the acct_id field. Since the incidents.assigned field and the accounts.acct_id field both refer to the same information (a staff account ID), the incidents and accounts tables can be joined together. As a result, joining these tables allows you to run reports or use views that include data from both tables, such as the number of incidents assigned to each staff member.
The simplified incidents and accounts tables listed below will be used to better illustrate the differences between inner and outer joins.
The specific data that is included in the query result depends on whether an inner or outer join is used in the query. If you select Toggle Join Type when working with the table instances in a view or report, the type of join will change from an inner join to an outer join or from an outer join to an inner join. To change the type of join between the tables, right click on the lower of the two tables and select Toggle Join Type.
The icon of overlapping circle indicates which type of join is used between the tables. If only the intersection of the circles is shaded, the join is an inner join. If the entire left circle is shaded, the join is an outer join. To see more specific information about how the tables are joined, right click on the table name and select Node Info.
An inner join returns data from the query ONLY if the value in the field in the first table also appears as a value in the field of the second table. This means that data must exist in both fields in both tables in order for the data to be returned in the query.
With inner joins, the ordering of the tables has no effect on the resulting data set.
Example: Using the case of the incidents and accounts tables, if the inner join is used, the query result will include ONLY the incidents that are assigned to a staff member. Incidents that are unassigned do not have a value in the accounts table, which means those incidents are not included in the result set. Similarly, staff members that do not have incidents assigned to them will not appear in the query results since they do not have incidents.
Note: With the inner join, incident 004 does not appear in the query results (because it is not assigned to a staff member) and Jim and Paula are not listed in the dataset because they do not have incidents assigned to them.
An outer join is also referred to as a left join. With an outer join, the query results include all of the data from the first table, and where the data exists in the second table, data from the second table is included as well for each record. With an outer join, it is possible that the row of data returned includes only the information from the first (or left) table. Null values can exist for the fields associated with the second table.
When working with outer joins, the ordering of the tables is very important. The resulting dataset is quite dependent on which table is listed first for the join.
Example: Using the simplified incidents and accounts tables, an outer join with the incidents table as the first table...
Note: With this outer join, incident 004 is included in the results. Paula and Jim do not appear in the results since they cannot be associated with any of the incidents.
Example: Using the simplified incidents and accounts tables, with the accounts table as the first table...
Note: With this outer join, Jim and Paula ARE listed in the dataset, even though they do not have incidents assigned to them. Incident 004 is not included in the results because it cannot be associated with a staff member.
Para obtener información adicional, consulte la sección 'Types of Table Joins' en la documentación en línea para la versión que su sitio está ejecutando actualmente. Para acceder a los manuales y la documentación en línea de Oracle B2C Service, consulte la Documentación de los productos de Oracle B2C Service.