Option to prevent saturation of an entity and corrupted data

Nicolas CHIGROS
Nicolas CHIGROS Active Partner
Fourth Anniversary 250 Up Votes 25 Likes 10 Comments
edited July 2021 in Idea Exchange
Add an option to prevent datareader from loading data into a saturated entity and a second option to stop if creating an member would result in a saturated entity.


PS : If this should be separated options fromi"On Error Stop" since we might want all rejected data logged into .log file and not stop at the 1st one, yet not have a corrupt database.
4
4 votes

Released · Last Updated

Comments

  • Sergi Fernández
    Sergi Fernández Active Partner, Community Captain
    100 Up Votes 10 Comments Second Anniversary 5 Likes

    Hi @Product Management Team

    I was looking into posts about prevention of entity saturation and came across this idea.
    I see that it's labeled as "Released" in July 2021, but don't recall any functionality similar to this one in Board.

    Can you confirm that this has been developed and added to Board? Where can it be found?

    Thank you,
    Best regards,

  • Helmut Heimann
    Helmut Heimann Employee, Community Captain
    500 Comments 250 Likes Fourth Anniversary 25 Answers
    edited October 30
    https://community.board.com/discussion/comment/18824#Comment_18824

    Hi @Sergi Fernández ,

    this has not been released as an option itself, but a DataReader populating an entity which would be "over-saturated" will be stopped and an according message will be written to the logs.

    You can find that here:
    https://help.board.com/v14/docs/en/running-and-managing-data-reader-protocols?highlight=max%20item

    image.png

    Best,
    Helmut

  • Nicolas CHIGROS
    Nicolas CHIGROS Active Partner
    Fourth Anniversary 250 Up Votes 25 Likes 10 Comments

    It was a great addition when it was implemented and it brought peace of mind on some data model.

    I'm sure that every board developer that had a corrupted data before that can relate ;)

Categories