Ex-QB Mark Sanchez arrested, faces three possible charges

Former NFL quarterback and current Fox Sports broadcaster Mark Sanchez was arrested by the Indianapolis Metropolitan Police Department on Saturday and is facing three misdemeanor charges in relation to an incident where he was stabbed and taken to a hospital.

The IMPD said Sanchez was arrested at the hospital on suspicion of battery with injury, unlawful entry of a motor vehicle and public intoxication. No further individuals are being sought by detectives. The Marion County Prosecutor's Office will make the final charging decision, the IMPD said.

Sanchez is still hospitalized and has not yet been booked into a detention center. Earlier Saturday, Fox Sports said in a statement that Sanchez is recovering and in stable condition.

"We are deeply grateful to the medical team for their exceptional care and support. Our thoughts and prayers are with Mark, and we ask that everyone please respect his and his family's privacy during this time," Fox Sports said in its earlier statement.

The IMPD earlier said it was investigating an incident between two men that took place at approximately 12:30 a.m. Saturday. The IMPD did not identify the men in its earlier statement but said one man received lacerations while the other man received injuries consistent with stab wounds.

Detectives reviewed video footage of the confrontation, which police said occurred in the popular downtown nightlife Wholesale District next to the Indiana statehouse.

Sanchez was scheduled to be part of the broadcast crew for Sunday's contest between the Las Vegas Raiders and Indianapolis Colts at Lucas Oil Stadium but will no longer work the game.

Sanchez, 38, played eight seasons in the NFL after being selected fifth by the New York Jets in the 2009 draft out of USC. He helped the Jets to back-to-back AFC Championship Game appearances in his first two seasons.

"Sending our thoughts and love to Mark Sanchez and his family. Hoping for a speedy recovery, 6," the Jets posted to X, using Sanchez's former jersey number.

Sanchez also played for the Philadelphia Eagles, Dallas Cowboys and Washington, the team he last appeared in a regular-season game for in 2018.

 

USC fans' dream of UCLA football going 0-12 dies as Bruins stun Penn State

With the Trojans off this week, USC fans had the opportunity to pay more attention to other college football games. One of the games that I suggested watching this week was UCLA vs. Penn State, as the Bruins continued on their quest for a historic 0-12 season.

Well, the dream is officially dead. In one of the most stunning college football results in recent memory, UCLA knocked off the Nittany Lions, winning the game 42-37.

Obviously, this was an absolutely disastrous loss for Penn State. But from a USC perspective, it was rather heartbreaking, too. With the Trojans coming off of a frustrating loss to Illinois, there have been a lot of questions over the past week about if this will be yet another underachieving season for Lincoln Riley's team. However, despite their team's struggles, one thing that USC fans have had to be excited about was the legitimate possibility that the school across town could finish the regular season 0-12—an infamous feat that would have hovered over Westwood for decades.

So much for that. Regardless of how the rest of the year plays out, UCLA will not go winless in 2025.

Perhaps the most jarring part of the game was that, after four weeks of completely lifeless play, the Bruins actually looked like a competent football team

This article originally appeared on Trojans Wire: UCLA football will not go 0-12, to the disappointment of USC fans

 

Ex-QB Mark Sanchez arrested, faces three possible charges

Former NFL quarterback and current Fox Sports broadcaster Mark Sanchez was arrested by the Indianapolis Metropolitan Police Department on Saturday and is facing three misdemeanor charges in relation to an incident where he was stabbed and taken to a hospital.

The IMPD said Sanchez was arrested at the hospital on suspicion of battery with injury, unlawful entry of a motor vehicle and public intoxication. No further individuals are being sought by detectives. The Marion County Prosecutor's Office will make the final charging decision, the IMPD said.

Sanchez is still hospitalized and has not yet been booked into a detention center. Earlier Saturday, Fox Sports said in a statement that Sanchez is recovering and in stable condition.

"We are deeply grateful to the medical team for their exceptional care and support. Our thoughts and prayers are with Mark, and we ask that everyone please respect his and his family's privacy during this time," Fox Sports said in its earlier statement.

The IMPD earlier said that it was investigating an incident between two men that took place at approximately 12:30 a.m. Saturday. The IMPD did not identify the men in its earlier statement but said one man received lacerations while the other man received injuries consistent with stab wounds.

Detectives had reviewed video footage of the confrontation, which police said occurred in the popular downtown nightlife Wholesale District next to the Indiana statehouse.

Sanchez was scheduled to be part of the broadcast crew for Sunday's contest between the Las Vegas Raiders and Indianapolis Colts at Lucas Oil Stadium but will no longer work the game.

Sanchez, 38, played eight seasons in the NFL after being selected fifth by the New York Jets in the 2009 draft out of USC. He helped the Jets to back-to-back AFC Championship Game appearances in his first two seasons.

"Sending our thoughts and love to Mark Sanchez and his family. Hoping for a speedy recovery, 6," the Jets posted to X, using Sanchez's former jersey number.

Sanchez also played for the Philadelphia Eagles, Dallas Cowboys and Washington, the team he last appeared in a regular-season game for in 2018.

 

Trump govt considers imposing travel ban on 43 nations, Pakistan is one of them: Report

Trump govt considers imposing travel ban on 43 nations, Pakistan is one of them: Report 

US diplomatic and security officials laid out a draft list recommending the list of countries whose nationals will be under the radar. This list is divided into three categories: 

Red, Orange and Yellow

US President Donald Trump’s administration is reportedly considering targeting the citizens of as many as 43 countries as part of a new travel ban to the United States. With this, the Trump government plans to broaden the restrictions imposed during his first time. According to The New York Times, US diplomatic and security officials laid out a draft list recommending the list of countries whose nationals will be under the radar.

This list is divided into three categories. 

They are as follows:

Red - All travel banned

Orange - Visas sharply restricted

Yellow - 60 days to address concerns

The red category has 11 countries whose citizens would be barred from entering the United States. These nations are; Afghanistan, Bhutan, Cuba, Iran, Libya, North Korea, Somalia, Sudan, Syria, Venezuela and Yemen. The official, who asked to remain anonymous told the New York Times that the list was developed by the US State Department several weeks ago.

#newsalert #latestnews #trump #trumppakistan

 

 

 

test

Paris 2024 Olympics athletics: Parul Chaudhary misses final despite season’s best, Jeswin Aldrin fails to impress

 

India’s Parul Chaudhary clocked a season’s best time in the qualification run but failed to make it to the women’s 3000m steeplechase final at the Paris 2024 Olympics on Sunday.

At the Stade de France, Parul Chaudhary, a two-time Asian Games medallist, finished eighth in her women’s 3000m steeplechase heat with a season-best time of 9:23.39. However, with only the top five athletes advancing, she failed to qualify for the final of the athletics event.

Meanwhile, Jeswin Aldrin recorded a best attempt of 7.61m in the men’s long jump qualification to finish 13th in his heat. He neither achieved the direct qualification standard of 8.15m nor did he finish among the top 12 athletes.

The 29-year-old Parul is the Indian national record holder in this event and clocked 9:15.31 at the World Athletics Championships in Budapest in 2023.

Not even her personal best would have assured Parul a spot in the final with the fifth-place qualifying athlete - Lomi Muleta of Ethiopia - clocking 9:10.73. Defending Olympic champion Peruth Chemutai of Uganda qualified in first place with 9:10.51.

This was the second event for Parul Chaudhary at Paris 2024. She also competed in the women’s 5000m race but couldn’t make the final after finishing 14th in her heat with another season’s best of 15:10.68. Parul also holds the national record in that event with 15:10.35.

In the men’s long jump qualification, Jeswin Aldrin’s first two attempts were ruled invalid before he landed a 7.61m jump with his final effort. It was an underwhelming performance from the long jump national record holder.

The 24-year-old achieved the 8.42m long jump national record at the Indian Open Jumps Competition in March last year.

#Olympics2024#Paris2024#RoadToParis#OlympicGames#ParisOlympics#GoForGold#AthletesInParis#OlympicSpirit#SportsForAll#OlympicDreams#ChasingGold#OlympicJourney#TeamUSA#OlympicHeroes#GamesOfTheXXXIII#ParisReady#OlympicFlame#InspireTheFuture#Paris2024Countdown

https://talhamanzoor2.blogspot.com/2024/08/paris-2024-olympics-athletics-parul.html#google_vignette

HOW TO EASILY INSTALL UPDATES TO XRMTOOLBOX TOOLS

Step-by-Step Guide to Install Updates to XrmToolBox Tools

To maintain optimal performance and access new features, it’s important to install updates to XrmToolBox tools regularly. This guide will walk you through the process step by step.

When you log into XrmToolbox, you may see the message “Updates are available for your tools”:

Continue Reading

channel

Dynamic CRM 365 JavaScript best practice

 Dynamic CRM 365 JavaScript best practice:  

These are the 5 refactorings I always do:

 Adding executionContext to functions;

Passing the executionContext is the new way to access Xrm.Page. Make sure you flag ‘Pass execution context as first parameter’. Waiting patiently for Microsoft to make this the default 

 Replacing var with let or const;

Using let or const prevents stupid bugs where you re-declare or overwrite variables when you didn’t mean to.

 Better names for variables;

While I’m replacing var, I also improve the names of the variables to make it clear what their intension is.

 Invert if statements and use early returns;

Remove all those nested if statements and make your code clearer to understand by returning immediately when a condition doesn’t apply or inverting the check in a if statement.

 Use async/await;

Remove promises and .then methods that are nesting your code and replace it with the async/wait pattern to improve your code readability.

Read More

How to use Autonumber field in Model Driven Apps

  How to use Autonumber field in Model Driven Apps

Autonumber fields are a type of field that automatically generates a unique, sequential number each time a new record is created in a Model-driven app. These fields are commonly used to assign unique identifiers to records, such as order numbers, invoice numbers, or case numbers. In this blog, we’ll explore how to use Autonumber fields in Model-driven apps.

To create an Autonumber field in a Model-driven app, follow these steps:

1. Navigate to the solution where you want to create the field.

2. Open the entity where you want to add the Autonumber field.

3. Select the “Fields” option from the left-hand menu, then click the “New” button.

4. Choose “Autonumber” as the field type and give it a name.

5. Choose the format of the Autonumber field. You can choose from a range of formats, including prefix, suffix, and separator.

6. Set the starting number and the increment value. The starting number is the first number that the Autonumber field will generate, while the increment value is the number that will be added to the previous number to generate the next number.

7. Choose the scope of the Autonumber field. You can set the field to be unique across all records in the system or unique within a specific record type.

Using an Autonumber Field:

Once you’ve created an Autonumber field, you can use it in your Model-driven app in a number of ways:

Display the Autonumber field on a form or view: You can add the Autonumber field to a form or view so that users can see the unique identifier for each record.

Use the Autonumber field in a workflow: You can use the Autonumber field in a workflow to trigger an action or send an email when a new record is created.

Filter records by the Autonumber field: You can filter records by the Autonumber field to find specific records more quickly.

Use the Autonumber field in a calculated field: You can use the Autonumber field in a calculated field to perform calculations on the unique identifier.

Export records with the Autonumber field: When you export records from a Model-driven app, the Autonumber field is included in the export so that you can easily identify and manage records.

Benefits of Using Autonumber Fields:

Using Autonumber fields in Model-driven apps can offer several benefits:

Easy identification of records: With a unique identifier for each record, it’s easier to identify and track records.

Efficient record management: Autonumber fields can help you manage records more efficiently by providing a way to sort and filter records.

Improved data accuracy: Autonumber fields can help ensure data accuracy by preventing duplicate records and providing a consistent format for records.

Increased productivity: With Autonumber fields, you can save time and reduce errors by automating the process of assigning unique identifiers to records.

Read More

Calculated fields considerations Dynamic CRM Fields

  Calculated fields considerations

You should be aware of certain conditions and limitations when working with calculated fields:

Saved queries, charts, and visualizations can have a maximum of 10 unique calculated fields.

The calculated field values are not displayed in the Customer Engagement Outlook Offline mode in the tile views or on entity main forms.

A maximum number of chained calculated fields is 5.

A calculated field can’t refer to itself or have cyclic chains.

If you change one of the condition operators in a multiple condition clause, all of the condition operators will update to that condition. For example, in the clause IF (x > 50) OR (y ==10) OR (z < 5), if you change the OR operator to the AND operator, then all OR operators in the clause will become AND operators.

You can access parental fields via the Lookup field to the parent entity, such as <LookupFieldName>.<FieldName>. This is not possible with multi-entity Lookup fields like Customer which can be Account or Contact. However, some entities have individual Lookup fields for a specific entity, such as ParentAccountid.<FieldName> or ParentContactid.<FieldName>.

Sorting is disabled on:

A calculated field that contains a field of a parent record.

A calculated field that contains a logical field (for example, address field).

A calculated field that contains another calculated field.

Calculated fields can span two entities only.

A calculated field can contain a field from another entity (spanning two entities – current entity and parent record).

A calculated field can’t contain a calculated field from another entity that also contains another field from a different entity (spanning three entities):

(Current Entity)Calculated Field <- (Parent Record) Calculated Field 1 <- (Parent Record) Calculated Field 2.

You can’t trigger workflows or plug-ins on calculated fields.

You can’t change an existing simple field to a calculated field. If your current application is using JavaScript or plug-ins to calculate a field, you would not be able to use the calculated fields feature without creating a new field.

Duplicate detection rules are not triggered on calculated fields.

A rollup can’t reference a calculated field that uses another calculated field, even if all the fields of the other calculated field are on the current entity.

Read More

A Custom Workflow Activity Plugin

  A Custom Workflow Activity Plugin is very similar to a Plugin exempt that it is executed from within a CRM Workflow, Whereas Plugins Are executed on Events that Occur on the Entity, So workflow Activities give you more control when the plugin will be executed as well as allowing you to configure some logic through the interface whereas a Custom Plugin has to be completely configured in Visual Studio and Plugin registration tool. Codeplex is full of usefull Custom Workflow Activities allowing you to overcome the limitations in CRM, so they are a create way for extending CRM for specific scenarios using Workflows.

wgen we are using Plugin we have a number of triggers availble(called as Steps/Message) to trigger the pluggin execusion,

where Custom workflows are triggered by standard workflows available in CRM,

that make the custom workflow triggers limited(Create, Updat, StatusChange, Delete and On assign).

So plugins have higher flexibility than workflows which makes it suitable for highly complex logics.

Where there are several opinion about this topic, i would state my thoughts as below,

Workflows are better when you need the operation needs to be configured periodically by non programmer administrator, where you can implement the configuration part as standard workflow (Workflow1), and static part of the functionality as custom workflow which will be executed by the standard workflow (workflow1).

Custom workflows has limited triggers when comparing to those of plugins, this is because Custom workflows need to be called from an OOB which can be triggered on create,update,delete or assign.

Plugins are richer in feature in terms of data bindings, triggers, execution ordering, which makes very high level of control over the operation and flexibility.

So in conclusion i would say if your scenario is not have big complexity in terms of triggers and operating modes or it needs some sort of reconfiguration needed by non programmers periodically go for Workflow/custom workflow else go for Plugins.

Read More

Difference Between Custom Workflow and Plugin:

  Difference Between Custom Workflow and Plugin:

When we are using Plugin we have a number of triggers availble (called as Steps/Message) to trigger the plugin execution,

Where Custom workflows are triggered by standard workflows available in CRM, that make the custom workflow triggers limited(Create, Update, Status Change, Delete and On assign).

Workflows and by extension, custom workflow activities, execute totally asynchronously.  Plugins can execute both asynchronously and synchronously.

Plugin overall execution time is lesser then workflows and if validations are required to be performed then plugins should be preffered.

Workflows can be manually executed, or automatically triggered by selected events.  Workflows can be limited to automatically execute within specific organizational scopes (ie. Org, BU, Parent and Child BUs, or for the Owner only).  Plugins are always triggered by the messages to which they’re subscribed, though some Messages allow limiting execution based on whether certain attributes have been passed into the Message.

Workflows can be turned off (by unpublishing).  Plugins are always on.  Custom workflow activities can be used in many Workflows.  Workflows can be developed through the Workflow design interface.  Plugins must be developed in Visual Studio.  Workflows do not require compiling (though custom workflow activities do).  Plugins and custom workflow activities must be compiled and deployed through processes external to CRM.

When speed of execution, security of process, and validity of data are integral, I choose Plugins.  When flexibility, functionality reuse, and optional user involvement are integral, I choose Workflows.

https://thepowerappsninja.com/2023/06/03/difference-between-custom-workflow-and-plugin/

Microsoft Dynamic CRM Marketing

 Customer Journey 

In Dynamics 365 Marketing, a Customer Journey is an automated marketing campaign intended for a specific target audience. With a drag-and-drop journey designer, marketers create a customized pipeline or path consisting of steps to send personalized email messages, schedule follow up activities for sales team members, trigger workflows, and execute campaign-related activities. As each member of the target segment progresses down the path, their reactions and interactions are tracked in the system, providing insight into the true reach and effectiveness of the marketing initiative.

Segments 

Segments let you create groups of related contacts that you can target with customer journeys. Segments are created using the segment designer. One way to build segments is by querying across related entities including contacts, leads, accounts, events, marketing lists, and more. You can also query the marketing-insights service to find contacts that have engaged with your marketing initiatives. The marketing-insights service also allows you to query contacts that you aren’t reaching because of issues such as email bounces.

Real time marketing:

Within real-time marketing you will have options to define journeys, event triggers, segments, consent center and more. Channels available include emails, push notifications and text messages.

Read More

What is Outbound Marketing?

 What is Outbound Marketing?

Outbound marketing is a broad term for messaging, advertisements, and other communications that attempt to attract sales lead prospects who might not be aware of your product, business, or service. Another distinction is that the typical recipient is not actively searching or shopping for what you are selling. This is why it is also known as interruption marketing. Your message interrupts or brings an unexpected awareness of your brand or product to the recipient’s attention. Modern outbound marketing efforts include unsolicited phone calls, cold email marketing campaigns, posts and promoted social media campaigns, and advertisements on websites.

What is Inbound Marketing?

Inbound marketing offers valuable content and resources on topics and products as a way to attract prospective buyers or customers, build brand awareness and authority, and drive lead conversions that translate into sales and revenue. Inbound marketing uses search engine optimization, landing pages, custom content assets, social media campaigns, and more to guide prospects down the buyer journey. Inbound marketing uses different channels than traditional outbound marketing (billboards, mailers, radio and t.v. ads) and offers prospective clients something valuable based on what they are searching for (instead of broadcasting a message to the general public).

Read More

Powerapps Portal Field Mandatory

 On click of the Next/Submit button, a function named entityFormClientValidate is executed. You can extend this method to add custom validation logic.

if (window.jQuery) {

   (function ($) {

      if (typeof (entityFormClientValidate) != ‘undefined’) {

         var originalValidationFunction = entityFormClientValidate;

         if (originalValidationFunction && typeof (originalValidationFunction) == “function”) {

            entityFormClientValidate = function() {

               originalValidationFunction.apply(this, arguments);

               // do your custom validation here

               // return false; // to prevent the form submit you need to return false

               // end custom validation.

               return true;

            };

         }

      }

   }(window.jQuery));

}

Read More