Best way for New UX users to add/delete list members when lists are sourced from Data Hub


I'm designing a new project and the lists and list details will reside in flat lists and system modules within the data hub. I've used forms on the New UX in past projects to allow users to create list members and assign parents. I've also created system modules for them to edit attributes of these list members.

My question is: what's the best setup to allow New UX users to create/delete list members and edit their attributes when the lists are sourced from the Data Hub?

Best Answer

  • umangsinghal

    @MatthewSweere Delete and Reload in Spoke models could be downtime for users and it can impact performance as well because the process will take a good amount of time for full load.

    If deletion is not very frequent and is less then you can create a Clear Flag in the Datahub and import this to your spoke model. In spoke model filter your view by excluding Clear Flag. It would exclude the deleted items from the view of users. OR You can delete the list member using "Delete from list using selection" action in both Hub and Spoke model. Clear flag will help you here to find the list members for deletion. First import the clear flag in spoke then Delete it in Datahub then delete it in Spoke model.

    Hope this helps!



  • In this case, you must create/ delete list members in Datahub and then update your spoke model based on Datahub. Create a page sourced to Datahub and give users ability to add/ delete list members.


  • @Umang Singhal Great, thank you for the advice. Would you recommend making that action part of a process that reloads the list info from Data Hub → Spoke? Or just wait for the next refresh? I know the former would be more convenient for users, but I'm wondering how detrimental it could be to model performance if we're potentially loading from Data Hub → Spoke throughout the work day