This message was deleted.

I apologize, but I don't have enough specific information to provide a detailed answer about adjusting code for a custom UI with the MongoDB connector. The knowledge sources don't contain information about custom UIs or frontend structures for Airbyte. However, I can provide some general information that may be helpful: 1. Airbyte's MongoDB source connector outputs data in a specific format, with fields like

_id

,

_airbyte_emitted_at

, and

_airbyte_data

[as described in the documentation](https://docs.airbyte.com/integrations/destinations/mongodb#output-schema-for-destination-mongodb). 2. If you need to modify how the data is structured, you may want to consider using transformations. Airbyte supports transformations using dbt, which could help reshape the data to fit your frontend structure [as mentioned in this forum post](https://discuss.airbyte.io/t/1888). 3. For more specific issues or customizations with the MongoDB connector, you might need to modify the connector itself. This can be done by building a custom version of the connector [as explained in this forum post](https://discuss.airbyte.io/t/1812). If you need more specific guidance, you may want to provide more details about your custom UI and the exact data structure you're trying to achieve. Additionally, consulting Airbyte's documentation or reaching out to their support channels might provide more tailored assistance for your use case.