Status & Status Reason Fields in Dataverse: What You Need to Know

Поділитися
Вставка
  • Опубліковано 2 гру 2024

КОМЕНТАРІ • 9

  • @kishorjadhav1801
    @kishorjadhav1801 Рік тому +1

    Very Useful 👍👍

  • @charlesopuoro5295
    @charlesopuoro5295 Рік тому

    Thanks a whole lot for this clear and enlightening video.

  • @2007pradipta
    @2007pradipta 5 місяців тому

    can we create Status Reason type of Field our own ? To field cascading ...

  • @BuLiGuT
    @BuLiGuT 6 місяців тому

    Hey,
    What can i do if i want to relate 2 status columns from different tables?
    I'm working with an Business Process Flow, and i want to change status reason on 2 tables, should i do this with an Power automate Flow ?

  • @Darasiemreap1
    @Darasiemreap1 Рік тому

    Thank you for this awesome video. Is there a way for users to input the reasons or comment field? i.e when a student is deactivated (dropped out).

  • @rohityadav3618
    @rohityadav3618 Рік тому

    Can you please help me how i can move my update of real time journey from dev to qa instance. For the first time I am able to move it from dev to qa but when i am trying to move an updated version of the journey from dev to qa i am getting an error "Cannot modify journey version number. Current version number 1 New version number 2"

  • @tristangeoffroy9286
    @tristangeoffroy9286 Рік тому

    Thank you. You advice to reuse this status field rather than creating a new one. Then how do you prevent the user to change the status by himself, as he is provided with activate/desactivate command bar action by default?

    • @softchieflearn
      @softchieflearn  Рік тому

      Put status and status reason field on form header so that user can change

    • @tristangeoffroy9286
      @tristangeoffroy9286 Рік тому

      @@softchieflearn ;-) by « prevent » I meant I don’t want them to change it! And the standard command bar offers activate/desactivate.