home.social

Search

224 results for “updatecli”

  1. Merseyside Police weekly news round-up, 2 May 2026 – Birkenhead News

    For regular crime and police-related updatesVisit Merseyside Crimewatch and tap ‘Join’ Wirral man jailed for making indecent images…
    #Liverpool #UnitedKingdom #UK #GB #England #Headlines #News #Europe #EU #Bebington #Birkenhead #Britain #Bromborough #Eastham #GreatBritain #Heswall #Hoylake #NewBrighton #NewFerry #RockFerry #Seacombe #Wallasey #WestKirby
    europesays.com/uk/932729/

  2. A South Sudanese man grabbed (hugged) an 18-year-old Iranian girl waiting for subway in Hamburg and jumped onto the subway tracks in front of the incoming train.
    UPDATEL: The images were reported as AI, I have checked and verified that they are not.

    According to published reports, both died instantly!
    Report (in English) at:
    deutschlandinenglish.com/p/tra

    #Germany #MentalHealth #MurderSuicide #Hamburg #Iran #SouthSudan #EUpol #Crime #Politics #Tragedy

  3. HERE IS YOUR #bash history #recap / #rewind / #year_in_review !!!

    grep -v "^[[:space:]]*#" ~/.bash_history |sed -E 's/^ *(sudo|doas) *//g' |awk '{print $1}' |sort |uniq -c |sort -n |tail -n $((LINES-2))
    

    Example from this laptop:

      54 updateall
      57 nsxiv
      58 pipx
      63 pkg_info
      73 tail
      92 git
     106 ssh
     109 w3m
     110 less
     127 echo
     138 type
     194 searchall
     214 grep
     225 ststatus
     275 duck
     286 ll
     292 vi
     341 man
     433 cd
     453 ls
    

    (Of course, it's not strictly a YEAR in review. Bash can timestamp the history, but most people don't have that turned on by default)

    #YearInReview

  4. The Infectious Disease Society of America is now recommending AGAINST the use of #covid convalescent plasma for almost all patients: idsociety.org/practice-guideli

    That's a stronger recommendation than in the February guidelines. The #IDSA is now advising almost everyone not to use convalescent plasma, including all hospitalized patients.

    I'm disappointed, but if a something is unlikely to help and might be harmful, I want to know that.

    #convalescentPlasma

  5. The Infectious Disease Society of America is now recommending AGAINST the use of #covid convalescent plasma for almost all patients: idsociety.org/practice-guideli

    That's a stronger recommendation than in the February guidelines. The #IDSA is now advising almost everyone not to use convalescent plasma, including all hospitalized patients.

    I'm disappointed, but if a something is unlikely to help and might be harmful, I want to know that.

    #convalescentPlasma

  6. The Infectious Disease Society of America is now recommending AGAINST the use of #covid convalescent plasma for almost all patients: idsociety.org/practice-guideli

    That's a stronger recommendation than in the February guidelines. The #IDSA is now advising almost everyone not to use convalescent plasma, including all hospitalized patients.

    I'm disappointed, but if a something is unlikely to help and might be harmful, I want to know that.

    #convalescentPlasma

  7. The Infectious Disease Society of America is now recommending AGAINST the use of #covid convalescent plasma for almost all patients: idsociety.org/practice-guideli

    That's a stronger recommendation than in the February guidelines. The #IDSA is now advising almost everyone not to use convalescent plasma, including all hospitalized patients.

    I'm disappointed, but if a something is unlikely to help and might be harmful, I want to know that.

    #convalescentPlasma

  8. The Infectious Disease Society of America is now recommending AGAINST the use of #covid convalescent plasma for almost all patients: idsociety.org/practice-guideli

    That's a stronger recommendation than in the February guidelines. The #IDSA is now advising almost everyone not to use convalescent plasma, including all hospitalized patients.

    I'm disappointed, but if a something is unlikely to help and might be harmful, I want to know that.

    #convalescentPlasma

  9. 🎉 C.IM has been upgraded to Mastodon 4.4.1!

    ✔️ New quote post support
    ✔️ “Followers you know” widget
    ✔️ Improved performance with Vite
    🛠️ Plus C.IM custom features: 5000-char toots, bigger uploads, and more!

    🔗 Read full update s.ee/gMqH

    #Mastodon #Fediverse #CIM #UpdateLog #OpenSource

  10. When Your DMLs Have Criteria Conditions Other Than Id

    The Update Records element in Salesforce Flow is a powerful tool that allows you to modify existing records without writing any code. It’s commonly used to change field values and update statuses. You can configure it to update a specific record (like a record from the trigger or a record you’ve retrieved in a prior element), or you can set conditions to update multiple records that meet certain criteria. Best practice is to keep your updates efficient. Limit the number of records updated when possible, and always ensure that your flow logic avoids unnecessary updates to prevent hitting governor limits or creating infinite loops. Use it thoughtfully to streamline processes and maintain clean, accurate data.

    Update Records

    When you update records, there are three ways you can configure the update element:

    1. Update using Id(s): Your update element can point to one record Id or multiple record Ids using the IN operator when executing the update. This is an efficient alternative, as the record(s) are uniquely identified. This alternative consumes one DML against your governor limit.
    2. Update using a collection: This method is efficient, because the update element always consumes one DML against your governor limit, regardless of how many records your are updating in one show. You can update up to 10K records in one update element.
    3. Update using criteria conditions for field values other than Id: When updating multiple records, we can also set conditions and update all the records that meet the conditions. In this case, Salesforce queries the database and gets the records that will be updated, and performs the update. This method therefore consumes one SOQL and one DML against your governor limit. It is possible that one or no record meets the conditions, as well.

    Update Using Criteria Conditions For Field Values Other Than Id

    Let’s expand on the last method. For an inactive account, you may want to update all open cases to closed status. In a flow we could configure the update element with the following conditions:

    • AccountId = Inactive Account
    • Closed = false (case status is not closed)

    And for these accounts the field update that will be performed is as follows:

    Status = Closed (set status to closed)

    In this scenario, what Salesforce will do is query and find the records using the two conditions listed above (SOQL) and set the Status field on these records to Closed (DML).

    Now, is this a bad thing? Not necessarily. This is a little known fact, that you should keep in mind when optimizing your flow for governor limit usage.

    What is the alternative? I guess you could perform an update using one of the other alternatives listed above. Let’s look at these alternatives in detail:

    Update Using Id(s)

    If you wanted to use this method you could get the records according to the criteria conditions, and extract the Ids and put them into a text collection using the transform element, and do the update using the IN element. This alternative is more complicated. It does not bring any efficiencies.

    Update Using a Collection

    You could get a collection of records using the conditions, loop through each item to update the case status, or possibly use the transform element to update the status in one shot – depending on your use case – then go to update using the processed collection. Too complicated. This alternative still uses one SOQL and one DML.

    Conclusion

    Updates that include conditions beyond specifying the Id of the record consume one SOQL and one DML against your execution governor limits; make sure you check and control your governor limit usage.

    Explore related content:

    Salesforce Flow Best Practices

    Flow Naming Convention Tips

    Can You Start With a Decision Inside Your Record-Triggered Flow?

    How Many Flows Per Object?

    #Automation #DML #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceTutorials #UpdateElement

  11. When Your DMLs Have Criteria Conditions Other Than Id

    The Update Records element in Salesforce Flow is a powerful tool that allows you to modify existing records without writing any code. It’s commonly used to change field values and update statuses. You can configure it to update a specific record (like a record from the trigger or a record you’ve retrieved in a prior element), or you can set conditions to update multiple records that meet certain criteria. Best practice is to keep your updates efficient. Limit the number of records updated when possible, and always ensure that your flow logic avoids unnecessary updates to prevent hitting governor limits or creating infinite loops. Use it thoughtfully to streamline processes and maintain clean, accurate data.

    Update Records

    When you update records, there are three ways you can configure the update element:

    1. Update using Id(s): Your update element can point to one record Id or multiple record Ids using the IN operator when executing the update. This is an efficient alternative, as the record(s) are uniquely identified. This alternative consumes one DML against your governor limit.
    2. Update using a collection: This method is efficient, because the update element always consumes one DML against your governor limit, regardless of how many records your are updating in one show. You can update up to 10K records in one update element.
    3. Update using criteria conditions for field values other than Id: When updating multiple records, we can also set conditions and update all the records that meet the conditions. In this case, Salesforce queries the database and gets the records that will be updated, and performs the update. This method therefore consumes one SOQL and one DML against your governor limit. It is possible that one or no record meets the conditions, as well.

    Update Using Criteria Conditions For Field Values Other Than Id

    Let’s expand on the last method. For an inactive account, you may want to update all open cases to closed status. In a flow we could configure the update element with the following conditions:

    • AccountId = Inactive Account
    • Closed = false (case status is not closed)

    And for these accounts the field update that will be performed is as follows:

    Status = Closed (set status to closed)

    In this scenario, what Salesforce will do is query and find the records using the two conditions listed above (SOQL) and set the Status field on these records to Closed (DML).

    Now, is this a bad thing? Not necessarily. This is a little known fact, that you should keep in mind when optimizing your flow for governor limit usage.

    What is the alternative? I guess you could perform an update using one of the other alternatives listed above. Let’s look at these alternatives in detail:

    Update Using Id(s)

    If you wanted to use this method you could get the records according to the criteria conditions, and extract the Ids and put them into a text collection using the transform element, and do the update using the IN element. This alternative is more complicated. It does not bring any efficiencies.

    Update Using a Collection

    You could get a collection of records using the conditions, loop through each item to update the case status, or possibly use the transform element to update the status in one shot – depending on your use case – then go to update using the processed collection. Too complicated. This alternative still uses one SOQL and one DML.

    Conclusion

    Updates that include conditions beyond specifying the Id of the record consume one SOQL and one DML against your execution governor limits; make sure you check and control your governor limit usage.

    Explore related content:

    Salesforce Flow Best Practices

    Flow Naming Convention Tips

    Can You Start With a Decision Inside Your Record-Triggered Flow?

    How Many Flows Per Object?

    #Automation #DML #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceTutorials #UpdateElement

  12. FOSS cellular projects are converging. After CFSB support in both #osmocom and #nextepc some months ago, I now have just successfully performed the first Authentication + UpdateLocation from 4G RAN to our 2G/3G OsmoHLR!