.NET Developer (Real Estate ERP Bug Fixing
$30-250 USD
Posted 1 minute ago
•
Ends in 6 days
$30-250 USD
Paid on delivery
Our in-house Real Estate ERP, built on ASP.NET / C# (.NET 6 with a mix of legacy .NET Framework services), has started behaving oddly: during lead assignment the wrong user or lead details are being pulled in, and the same logic sometimes blocks us from updating existing leads. I need an experienced .NET developer who can step through the code, trace the root cause, and deliver a clean, tested fix that leaves the rest of the system untouched. You will have access to the Git repository, SQL Server database, and the API layer that handles lead workflows. I expect you to reproduce the problem, isolate the faulty logic or data mapping, patch it, and prove that: • Assigning a new lead now links the correct user and preserves the right lead information. • Updating an existing lead saves accurately and loads without corruption. • No other modules (reporting, billing, mailer, etc.) regress after the change. Please use proper debugging tools (Visual Studio, SQL Profiler, Postman or similar) and commit clean, well-commented code that follows our current architecture. Unit or integration tests covering the fixed scenarios are a plus. If this sounds straightforward to you and you are comfortable with .NET 6, Entity Framework, RESTful APIs, and agile pull-request workflows, let’s get started—I’ll provide branch access and a short functional walkthrough as soon as you accept.
Project ID: 40819525
About the project
48 proposals
Open for bidding
Remote project
Active 3 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
48 freelancers are bidding on average $111 USD for this job


Hi, I understand that the ERP is mixing up users or lead details during assignment and may reject valid updates. I will reproduce both cases from the API and database flow, step through the ASP.NET and C# code, check Entity Framework mappings and SQL queries, then make the smallest safe fix. I will verify lead assignment, existing lead updates, and related modules so reporting, billing, and mailer flows stay unchanged. I can add focused Software Testing coverage, commit clear changes in Git, and keep the patch aligned with your current .NET 6 and legacy service structure. Can you share the failing lead IDs or exact steps, plus whether the issue occurs in .NET 6, legacy services, or both? Please start the chat and let’s discuss the branch setup and functional walkthrough.


The key here is finding why assignment and updates both pull in the wrong lead or user data, then fixing that shared cause without disturbing the rest of the ERP. I’ll reproduce both failures against known lead records and trace the API request through DTO mapping, Entity Framework tracking, SQL queries, and any legacy service involved. A reused tracked entity or incorrect join could explain both symptoms, but I’ll verify the cause before changing code. I’ll make a focused fix within your existing architecture, add regression tests for assignment and update where the test setup allows, and verify that saved leads reload correctly. I’ll also run the available test suite and targeted checks around reporting, billing, and mailer dependencies. You’ll receive a clean pull request with the root cause, test results, and any remaining risks documented. Please share the branch, walkthrough, and one affected lead/user example so I can start with a reproducible case.


Hi, I've spent the last decade working on .NET systems like yours—mixed legacy and modern stack, data integrity issues in high-stakes workflows—so I know exactly how to approach this. I'll start by reproducing the lead assignment and update failures in your environment, then use Visual Studio and SQL Profiler to trace where the wrong user or lead data is being pulled, isolating whether it's an Entity Framework mapping issue, a query logic problem, or a data state problem. Once I've identified the root cause, I'll patch the faulty logic, add unit or integration tests around the fixed scenarios, and run through lead assignment and updates against real data to confirm the fix works and nothing else regresses. I'll commit clean, well-commented code following your current architecture and pull-request workflow. I'm available now and will stay on after delivery for any adjustments or follow-up questions that come up.


Hello, The issue with your Real Estate ERP involves incorrect user and lead assignments during lead workflows, which also affects updating existing leads. I would diagnose the faulty logic or data mapping to fix these assignment errors. Given my experience with ASP.NET, C#, and Entity Framework, I recommend a thorough review of your lead assignment logic. Utilizing debugging tools like Visual Studio and SQL Profiler will help isolate the root cause effectively. I will reproduce the issues, implement the necessary fixes, and ensure that assigning new leads correctly links the right users. I will also verify that existing leads update without corruption. The delivery will take 3 days at a budget of $30. Could you confirm if there are any specific modules that should be prioritized for regression testing? Please feel free to reach out to me. I look forward to working with you. Best regards, Billy Bryan


Hi there, I’ve read through your requirements for the Real Estate ERP bug fix and I’m confident I can help resolve the lead assignment and update issues you’re experiencing. With extensive experience in .NET (including .NET 6 and legacy Framework projects), C#, and Entity Framework, I’ve successfully diagnosed and fixed similar bugs in complex enterprise systems—always with an emphasis on precision and minimal disruption to unaffected modules. My approach will be to first reproduce the problem using your Git repository and database, leveraging Visual Studio’s advanced debugging tools alongside SQL Profiler and Postman to trace the exact flow of data during lead assignments and updates. Once I’ve pinpointed the faulty logic or data mapping, I’ll implement a targeted fix, ensuring all lead-related operations function correctly without side effects. I will also verify that adjacent modules like reporting, billing, and mailer remain stable, running regression checks as needed. To ensure long-term stability, I’ll add clear code comments and, where possible, write or update unit/integration tests to cover the fixed scenarios. I’m comfortable working within agile pull-request workflows and will keep my commits clean and well-documented for your review. I look forward to collaborating with you and getting your ERP system running smoothly again. Best Regards


Hello, Debugging a real-world ERP issue across C#, SQL Server, and API workflows is where my 15+ years of software development experience is most valuable. As the founder of A4Logic, I have built and supported ERP, CRM, SaaS, and REST API solutions, giving me the practical background to trace incorrect user/lead mappings and update failures without disturbing unrelated modules. My C# programming and Microsoft SQL Server skills align directly with your ASP.NET/.NET 6 system and its database-driven lead workflows. I focus on clean, maintainable code and can work within an existing architecture to isolate the faulty logic, correct the data handling, and add focused coverage for the affected scenarios where appropriate. My experience with REST APIs and business systems also supports reliable validation across the API and database layers. I am ready to take ownership of this bug fix and deliver a carefully scoped, tested, and cleanly committed solution. Thanks!


Hello, This symptoms points directly to a race condition or an improper entity tracking state inside your Entity Framework context during concurrent lead operations, likely compounded by how the legacy .NET Framework services interact with the .NET 6 API layer. When lead assignment pulls incorrect details or blocks updates, it usually means cached instances or detached entities are crossing boundaries in the repository pattern or improper async await usage is causing DbContext thread contamination. I will spin up Visual Studio and SQL Profiler to trace the exact execution path through the lead workflow controller and isolate where the data mapping diverges before pushing a targeted patch. What is the current isolation level set on your SQL Server database for these lead transactions? Have a nice day


Hi there, I see you need a seasoned .NET developer to address specific issues in your Real Estate ERP. I can help you reproduce the lead assignment problems and conduct thorough debugging using Visual Studio and SQL Profiler. Once the faulty logic or data mapping is identified, I will develop a tested solution ensuring new leads connect to the correct user and that updates function flawlessly without affecting other modules like reporting and billing. I’ll also ensure the code is clean and well-commented, in alignment with your architecture. Implementing unit tests covering the fixes is certainly doable. This approach not only resolves the immediate issues but also stabilizes the application moving forward. Regards, Ali


Hello, After reviewing your requirements, I understand the goal: fix lead assignment and updates without affecting other ERP modules. I have experience with ASP.NET/C#, Entity Framework, SQL Server, and REST APIs, and I’m available to start right away. The key challenge is tracing where user IDs or lead data become mismatched across .NET 6 and legacy services. I’ll reproduce both issues, use Visual Studio debugging, SQL traces, and Postman to isolate the faulty mapping or update logic, then make a focused patch within your current architecture. I’ll verify correct assignment, accurate updates and reloads, add targeted regression tests, and check related module workflows before submitting a clean, commented pull request. I have a couple of quick questions. • Do these issues affect all leads or only specific roles or records? • Is a staging database available for reproduction and regression testing? My initial estimate is $120 fixed and 1–2 days, subject to confirming the scope during your walkthrough. I would be glad to discuss the details and am ready to start immediately. Looking forward to hearing from you. Best regards, Carlos.


Legacy .NET Framework mixed with .NET 6 usually means the bugs live in the integration seams, not the code itself. I would pull the repo, reproduce the issues in Visual Studio against a copy of your SQL Server schema, and fix them one by one with test coverage so they stay fixed. Can start right now, first batch of fixes back within 48 hours. Budget and timeline here are rough based on the post, we will firm them up once I see the actual bug list. Want me to send a quick scope doc so we can get moving?


⚠️ If you're not happy, you don’t pay. ⚠️ Hi Client, thank you for sharing the detailed project brief. I can resolve your lead assignment issues using .NET 6, C#, and Entity Framework with a clean, efficient design. I will deliver: • Reproduced and diagnosed lead assignment and update issues • Isolated faulty logic or data mapping with a tested fix • Verified correct user-linking for new leads • Accurate saving and loading of existing leads • Regression checks on all modules (reporting, billing, mailer, etc.) • Clean, well-commented code committed to your Git repository • Unit tests for fixed scenarios to ensure ongoing reliability You will also receive comprehensive documentation and support for the implemented changes. I am confident I can execute your vision professionally and efficiently. Looking forward to discussing the timeline and next steps. Best regards, Chirag Pipal


Hi, 10+ years of building and debugging .NET backends with SQL and API integrations. I’ll reproduce the lead-assignment and lead-update anomalies by stepping through the .NET 6/ASP.NET C# workflow code, tracing entity mappings and REST API payloads, then validating the SQL Server data involved. Using Visual Studio for debugging and SQL Profiler for query tracing, I’ll isolate the incorrect user/lead selection or blocking logic, apply a minimal patch consistent with your existing services, and add targeted unit/integration tests for the fixed scenarios. I’ll also run a regression pass to confirm reporting, billing, and mailer modules remain unaffected. You’ll receive a clean, well-commented PR with tests and proof that new-lead assignment links correctly and existing-lead updates persist reliably. Best, Razmik


Debugging lead-assignment and update defects in an ASP.NET/C# ERP is a strong match for my .NET development background and skills in Microsoft SQL Server, REST APIs, and Visual Studio. I can work across the application and database layers to trace incorrect user or lead mappings, identify why existing records are blocked, and deliver a focused fix that respects your current architecture. My 10+ years of professional full-stack development experience support a careful approach to backend logic, API behavior, data handling, and maintainable code. I can also validate the corrected lead workflows through the REST API and SQL Server, while keeping attention on clean implementation and avoiding unnecessary changes to reporting, billing, and mailer modules. I would be glad to step into this codebase, isolate the root cause, and commit a tested, well-commented solution for your ERP. Choose me for focused .NET debugging and reliable software development.


Hello, I can investigate and fix the lead assignment and update issues in your ASP.NET/C# ERP. I’ll trace the API, Entity Framework queries, and SQL data mapping to identify the root cause, then implement a focused fix without disturbing existing modules. I’ll also test new lead assignments and existing lead updates, check for regressions, and commit clean, documented changes through your Git workflow. Please share the repository access, error examples, and steps to reproduce the issues so I can begin.


Hi, Melih here >> "REAL ESTATE ERP LEAD ASSIGNMENT AND UPDATE FIX" - you need the correct lead and user data saved without breaking other modules. I would trace the lead workflow from the ASP.NET API through the C# services and SQL queries to find where the wrong user or lead details are being mapped. I would reproduce both issues, check Entity Framework tracking and update logic, then make a focused fix that follows your existing architecture. I would also test new lead assignments, existing lead updates, and related workflows to check for regressions before committing the changes. Do you know whether the issue started after a recent code change or a database update? Looking forward to work with you.


Hi, I like this project because I realized what you want in this and have already found some technical solutions for it. Resolving subtle lead-assignment and update defects in a mixed .NET codebase requires more than patching the first failing line—it requires tracing the business logic, data flow, and architecture together. With 20+ years in software development as an Engineer, Senior Engineer, and Lead, I regularly rescue fragile legacy systems and build reliable APIs and database-backed applications. My ASP.NET, C#, and .NET expertise aligns directly with your ERP and API layer, while my experience with architecture, database design, optimization, and long-term system maintenance supports a careful fix that preserves existing modules. I can work independently through the repository and workflows, isolate the faulty mapping or logic, and deliver clean code consistent with your architecture. Agile development experience also fits your pull-request workflow, with tests around the corrected lead assignment and update scenarios where appropriate. I’m ready to bring senior-level debugging and rescue experience to this ERP and deliver a focused, maintainable correction without unnecessary changes elsewhere. Best, Shayne


Hello, I understand you need the lead assignment and lead update bugs traced to the root cause and fixed without disturbing the rest of the ERP. I’m confident I can help with this. I work on software development, .NET, SQL, and C# programming, and I’m comfortable stepping through mixed .NET 6 / legacy .NET Framework codebases, API layers, and SQL Server logic. Suggested stack: - ASP.NET / .NET 6 - C# programming - SQL Server - Entity Framework - RESTful APIs Plan: - Reproduce the issue and inspect the lead workflow end to end - Trace the faulty mapping, query, or state logic in code and SQL - Patch the root cause with minimal changes - Add unit or integration coverage for the fixed scenarios - Verify no regressions in reporting, billing, and mailer flows I’ll keep communication clear, work in small milestones, and provide clean, tested commits so you can review each fix before it’s finalized. If helpful, I can also leverage existing patterns in your codebase to move faster while keeping the architecture consistent. Would you like me to focus first on the lead assignment bug, or trace both workflows in parallel? If this sounds good, I’m ready to start and can begin as soon as branch access is shared. Best, Ruslan


Hello, I’m Legislatíva Lauko, with 10+ years of experience in Debugging, Software Development, REST API, and .NET-based systems, including ASP.NET, C#, Entity Framework, and legacy .NET Framework services. I understand the issue: the lead assignment and update flow is pulling the wrong data and blocking valid edits. I’ll reproduce the bug in Visual Studio, trace the API and SQL path, isolate the faulty mapping/logic, then patch it with clean, testable changes while keeping reporting, billing, and mailer modules untouched. Please start the chat so we can go through the flow and pinpoint the fix quickly. Regards, Legislatíva Lauko


Hello. From your description, I see that your main goal is to make lead assignment and lead updates reliable again, so the right user and lead details are always linked and saved, without side effects on reporting, billing or the mailer. With that in mind, I'd reproduce the issue in a test environment, trace the assignment and update flow through the API, Entity Framework mappings and SQL Server with Visual Studio and SQL Profiler, then fix the root cause in a small, commented pull request with unit and integration tests, and verify it with Postman scenarios and a regression pass over the neighbouring modules. Q1: Can you share an example lead where the wrong user or details appear, and when did it start, for example after a deployment or database change? Q2: Does the repository already have tests, and does the faulty logic sit in the .NET 6 code or in the legacy .NET Framework services? I'd appreciate your thoughts on this approach.


HELLO, ".NET Developer" - incorrect lead assignments and failed updates point to a problem in the workflow logic, data mapping, or Entity Framework tracking. I'll trace the lead assignment and update flow across the ASP.NET APIs, C# services, and SQL Server, reproduce both failures, isolate the root cause, and implement a targeted fix without disturbing unrelated ERP modules. I'll verify the changes with focused tests for lead ownership, data integrity, and existing-record updates, then commit clean code following your current architecture. Are the lead assignment and update issues occurring in the same API endpoint or in separate workflows? I appreciate your consideration and look forward to working with you. THANKS
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗